hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 8.5.2 Case 2: high business concentration areas | Table 19 reports the same calculations given in table 18. Also in this case we have considered the evening busy hour, since the evaluation of the total offered traffic shows that this is the busy hour of all the day also in such area. Table 19: Spectrum requirements (high business concentration area) City City/Urban Ur... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 8.6 Fixed link requirements | Any implementation of HIPERACCESS will require links between Access Point Transceivers (APT) and Access Point Controllers (APC) and beyond to core networks. TR 101 177 [3] points out that high capacity microwave links could be used to facilitate these connections. By way of an example, the Mean Busy Hour (MBH) traffic ... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 8.7 UMTS Spectrum Requirements | On the basis of the traffic model, described in [27], relevant to the "worst case" UMTS traffic for central business district, foreseen for the year 2005, the following tables estimate the spectrum requirement for the UMTS infrastructure. Table 20a Average HA DL net bit rate (Mbit/s) 90 Average HA UL net bit rate (Mbit... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 9 Radio aspects | This clause discusses aspects of the HIPERACCESS air interface, which needs particular attention. |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 9.1 Frequency bands and channel plans | Licensed versions of HIPERACCESS are expected to work in appropriate fixed service frequency bands. HIPERACCESS will be based on FDD and a TDD version will be specified based on the FDD standard. Support for H-FDD terminals interoperable with FDD is required. TDD operation would enable use to be made of unpaired freque... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 9.2 System co-ordination | HIPERACCESS systems will be deployed in frequencies and geographical areas adjacent to other radio systems. To a greater or lesser degree, deployment will have to be co-ordinated with these other systems Any frequency band allocated to HIPERACCESS and operator sub-divisions of the band should be defined so that operato... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 9.3 Spectrum sharing | The most common use of HIPERACCESS will be in licensed spectrum, where operators will have exclusive use of the assigned bands in particular regions. Since HIPERACCESS system requirements address both residential and business users and UMTS infrastructure, the quality of telecommunication services will be very high sta... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 9.4 Multiple operators | It must be possible to support several viable operators in a given area in the core HIPERACCESS spectrum. The radio aspects of the design should consider various deployment scenarios and allow for appropriate guard bands and other features to permit this. |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 10 Interoperability aspects | The HIPERACCESS standard will support interoperation at the air interface. |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 10.1 Definition of interoperability | Interoperability means the ability of an Access Termination (AT) designed and built according to the standards to interoperate with an Access Point designed and built independently to the same standards and to provide defined services according to an "interoperation profile" specification. |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 10.2 Requirements for interoperability | For inter-operable systems, the following will be specified: • PHY layer specifications • DLC layer specifications • Interworking functions (to supported UNIs and SNIs) IWFs (InterWorking Functions) occur at two points. One type of IWF is required to translate the internal (B2) interface of the HIPERACCESS network into... |
4eb80c8c468736d26cfc26100cd7008b | 102 003 | 11 Requirements for co-existence | Spectrum mask The spectrum mask is defined in a frequency band around the centre frequency. It includes the useful bandwidth and the immediate bandwidth on either side of the useful bandwidth (for instance TM4 standards define the spectrum mask up to ± 250 % of the Channel Spacing on each side of the centre frequency).... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 1 Scope | The present document defines the requirements for radio frequency usage for TETRA Advanced Packet Service (TAPS). It includes necessary information to support the co-operation between ETSI and the Electronic Communications Committee (ECC) of the European Conference of Post and Telecommunications Administrations (CEPT),... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air Interface (AI)". [2] ETSI EN 300 392-3 (all sub-parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 3: Interworking at the Inte... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 3 Definitions and abbreviations | |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Air interface (Um interface): the interface between Mobile Station and TAPS network Gb interface: the interface between an SGSN and a BSS Gi interface: the interface between Packet Domain and an external packet data network Gn interfac... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Air Interface BCCH Broadcast Control Channel BSS Base Station System BTS Base Transceiver Station CDF Cumulitive Distribution Function DMO Direct Mode Operation EDGE Enhanced Data rates for GSM Evolution EGPRS EDGE GPRS (E)GPRS (Enhanced) G... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4 Executive summary | TETRA Advanced Packet Service (TAPS) has been developed in response to user needs and according to a mandate issued by the ETSI Board. The mandate outlined that TAPS should be developed as fast as possible by making maximum reuse from other standardized technologies. TAPS should also provide for Interworking and Roamin... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.1 Status of the present document | Version 0.0.6 was approved at ERM RM 7 - 10 January 2003 after review of the compatibility studies performed by CEPT SE. These compatibility studies cover all the concerns raised earlier. Concerns expressed by the GSM community (ETSI TC MSG) were confirmed by the compatibility studies performed by CEPT (see clause C.1)... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2 Technical issues | The following text is extracted from a TR 101 976: "Guide to TAPS". The guide serves as a quick way to understand what TAPS is about and what it covers. |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.1 Service requirements | TETRA Advanced Packet Service (TAPS) provides high-speed packet data at speeds approximately 10 times that available in existing TETRA, to support multimedia and other high-speed data applications required by existing and future TETRA users. TAPS enables the service subscriber to send and receive data in an end-to-end ... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.2 Overview of standardized interfaces | The existing TETRA standards define a number of interfaces to support mobile services as shown in figure 1. The central component of the standard reference model is the Switching and Management Infrastructure (SwMI) which provides circuit and packet switched telecommunication services to mobile stations (MS). ETSI ETSI... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3 Air interface | In order to add high-speed packet data services to the TETRA standard, a new air interface is added between the MS and network. This interface is referred to as Um with a protocol stack as shown in figure 3. The components of the protocol stack re-use, as far as possible, the (E)GPRS standards drafted by ETSI for GSM s... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.1 Classes of terminal | Class-C mode is the only GSM MS mode of operation supported, since all circuit switched channels, including speech channel, are outside the scope of TAPS. In class C mode, the MS is exclusively attached to the GPRS network. ETSI ETSI TR 102 001 V1.1.1 (2003-04) 13 |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.2 Service interaction | Service interaction with circuit switched channels is outside the scope of TAPS. |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.3 GSM standard references and deltas | The basis for TAPS is the following: • The specifications from 3GPP Release 1999, are used as the basis; • 77 specifications are wholly applicable; • 19 specifications are applicable in part, where some clauses are omitted; • 10 specifications contain modifications to individual clauses; • The technical changes fall in... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.3.1 Physical layer | (E)GPRS Transposition to TETRA environment The following text describes in general the adaptations to the physical layer for TAPS. Frequency bands and channel arrangement The TAPS standard is designed to cover the bands 380 MHz to 400 MHz, 410 MHz to 430 MHz, 450 MHz to 470 MHz, 870 MHz to 876/915 MHz to 921 MHz. These... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.3.2 Data link layer | The requirements are the same as for (E)GPRS. |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.3.3 RRC/RLC/MAC layer | The requirements are the same as for (E)GPRS, except that requirements associated with circuit-switched connections are deleted. |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.3.3.4 Mobility management and GPRS session management | The requirements are the same as for (E)GPRS, except that requirements associated with circuit-switched connections are deleted and that the Mobile Station Classmark and Mobile Station Radio Access Capability information elements are extended to address access to TAPS networks. |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.4 Interface to packet data networks | The Packet Domain can operate IPv4 or IPv6. The interworking point is the Gi interface. The Gi Reference point is the interface between the Packet Domain and an external packet data network. Gi TAPS core stack IP L2 L1 Figure 4: The protocol stacks for the IP/Gi reference point Typically in the IP networks, the interwo... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.5 Roaming between TETRA TAPS and TETRA V+D | This is outside the scope of TETRA TAPS at this time. |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.6 Roaming with GSM networks | This clause describes the basis for roaming/migration between TETRA TAPS and (E)GPRS networks. The high-speed packet data overlay allows a TETRA TAPS MS to obtain high-speed packet data services from a TETRA TAPS network. Given that this service is provided using (E)GPRS technology, it is desirable to facilitate interw... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.2.7 Implementation examples | Since TAPS references GSM (E)GPRS standards, there are various possible implementations that take advantage of (E)GPRS core network components and internal interfaces. Figure 6 shows one such implementation possibility which shows how TAPS may be implemented using such components. MS External IP packet data networks Um... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.3 Short background information | For completeness the output press release following the Board decision has been included. Further information is available on the ETSI Web Site under Board Meeting 28. New Terms of Reference for Release 2 of TETRA Approved by ETSI Board 28 The 28th ETSI Board meeting approved additional Terms of Reference (ToR) for the... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 4.4 Short market information | EPT has carried out market survey to identify what enhancements the users wanted for TETRA Release 2. Figure 9 shows the relative weighted importance of the new requirements: High-speed data New voice codec 10 % SIM enhancement 10 % Air interface enhancements 17 % Interworking and roaming 19 % 3rd party APIs 2 % 40 % O... |
6d348e4a451a78c137a9e62492c5cb5d | 102 001 | 5 Main conclusions | From the market information collected from the users it is clear that the most needed facility is high-speed data to complement the existing V+D services of TETRA. This is not a surprise because of all the applications becoming available from IT and the cellular market. The modern user is not prepared to carry several ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 1 Scope | The present document provides implementation guidelines for the use and implementation of the DVB Simulcrypt standard. It first tries to draw attention to the technical questions that need to be answered in setting up a DVB Simulcrypt head- end. It also provides guidelines which are intended to be highly recommended ru... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ISO/IEC 13818-1 (1994): "Information technology - Generic coding of moving pictures and associated audio information: Systems". [2] ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB sys... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 3 Definitions and abbreviations | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: broadcaster (service provider): organization which assembles a sequence of events or services to be delivered to the viewer based upon a schedule CA_system_id: uniquely and globally identifies a particular CA provider, as registered in... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Access Criteria bslbf bit string, left bit first C(P)SIG Custom PSI/SI Generator CA Conditional Access CAS Conditional Access System CAT Conditional Access Table CP Crypto Period CW Control Word CWG Control Word Generator DVB Digital Video ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 4 Architecture | The system architecture, in figure 1, shows the logical relationships between the components and which component-to-component interfaces are defined by the DVB Simulcrypt standard. Other components exist in a head-end which are not illustrated i.e. SMS. C(P)SIG SIMF Agent AC ECMG SIMF Agent EMMG SIMF Agent PDG SIMF Age... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 5.1 ECMG protocol | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 5.1.1 Differences between Version 1 and Version 2 | There are four differences between version 1 and version 2 of the ECMG protocol: • CW length (cf. CP_CW_combination parameter): in V1, CW are 8 byte long; in V2, the CW length is variable; • ECM_id: this parameter does not exist in V1 and is mandatory in V2; • CW_Encryption: this parameter does not exist in version 1 a... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 5.1.2 Recommendation for ECMG protocol compliance | A V1 + V2 configuration in a SCS/ECMG pair shall be avoided because it cannot work. A V1 + V1 configuration or a V2 + V2 configuration in a SCS/ECMG pair is recommended. If the SCS is compliant with V1 and V2, the SCS connects the ECMG in V2 mode. If the ECMG is V1-compliant, the following policy is recommended: • such... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 5.2 EMMG/PDG protocol | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 5.2.1 Differences between Version 1 and Version 2 | There are four differences between version 1 and version 2 of the EMMG/PDG protocol: • Data_id: this parameter does not exist in V1 and is mandatory in V2; • Data_provision message: in V2 the data_channel_id parameter and the data_stream_id parameter are optional, according to the data part protocol TCP or UDP; • Data_... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 5.2.2 Recommendation for EMMG/PDG protocol compliance | A V1 + V2 configuration in a EMMG/PDG/Mux pair shall be avoided because it cannot work. A V1 + V1 configuration or a V2 + V2 configuration in a EMMG/PDG/Mux pair is recommended. If the EMMG/PDG is compliant with V1 and V2, the EMMG/PDG connects the Mux in V2 mode. If the Mux is V1 compliant, the following policy is rec... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6 ECMG (SCS Protocol) | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1 State diagram | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.1 Channel state machine | This clause presents the channel state machine, which defines the sequence of channel-level messages that shall be used to establish and maintain one channel on one TCP connection. The channel state machine is found in figure 4. Each state found in this state machine is defined in clauses 6.1.1.1 to 6.1.1.4. Channel No... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.1.1 Channel Not Open | This state represents the initialization of the channel state machine. At this point, a TCP connection is assumed to be established and the channel has either not been initialized, or has been closed. The SCS initializes a channel by sending a channel_setup message to the ECMG on the other end of the channel. Channel_s... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.1.2 Channel Setting Up | From this state, the ECMG shall respond with either a channel_status or a channel_error message. The channel_status message acknowledges successful channel establishment, and that the channel is open. The ECMG also indicates, via this message, several CAS specific parameters, particularly the maximum number of streams ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.1.3 Channel Open | This state represents the steady-state operation of the channel state machine. As long as the channel is open and error-free, streams may be opened, used and closed, per the stream state machine defined in clause 3.1.2: the stream state machine defines the stream-level and data-level messages that can be sent on a stre... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.1.4 Channel In Error | This temporary and short-lived state is used only to represent the fact that the ECMG has encountered and reported an unrecoverable channel error. The SCS shall close the channel. The SCS sends a channel_close message to the ECMG. Transmission and receipt of channel_close move the state machine to the Channel Not Open ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.2 Stream state machine | The head-end can establish one or more streams within a channel. This clause presents the stream state machine, which defines the sequence of stream-level messages that shall be used to establish, maintain and use a single stream within a channel. Streams may be established in any order (within a given channel, or glob... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.2.1 Stream Not Open | This state represents the initialization of the stream state machine. At this point, the stream has either not been initialized, or has been closed. The channel in which the stream is found shall be in the Channel Open state in order to proceed. The SCS initializes a stream by sending a stream_setup message to the ECMG... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.2.2 Stream Setting Up | From this temporary and short-lived state, the ECMG shall respond with either a stream_status or a stream_error message. The stream_status message acknowledges successful stream establishment, and that the stream is open. Transmission and receipt of stream_status move the state machine to the Stream Open state. The str... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.2.3 Stream Open | The stream is open and operational. Five kinds of stream-level messages can be sent while in Stream Open state: • The SCS sends a CW_provision message to request the ECMG an ECM. This message carries control word(s), access criteria and cryptoperiod numbers. The ECMG shall respond to each CW_provision message with an E... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.2.4 Stream In Error | This temporary and short-lived state is used only to represent the fact that the SCS or the ECMG has encountered and reported an unrecoverable stream error. The SCS sends a stream_close_request message to the ECMG. Transmission and receipt of stream_close_request move the state machine to the Stream Closing state. ETSI... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.2.5 Stream Closing | This temporary and short-lived state is used only to represent the fact that the SCS has requested closure of the stream. The ECMG sends a stream_close_response message to the SCS, to confirm closure of the stream. Transmission and receipt of stream_close_response move the state machine to the Stream Not Open state. Th... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.1.3 Summary of messages permissible in each state | Table 1 provides a listing of the channel-level and stream-level messages that may be generated in each of the states of both state machines. Table 1: message/state cross-reference for the SCS ⇔ ⇔ ⇔ ⇔ ECMG state machines Channel states Stream states (if Channel Open) Messages Not open Setting up Open In error Not open ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 6.2 Network delay | In any head-end architecture there is the option of connecting CA systems to scramblers at remote sites over a wide area network. In this situation, in order to be more meaningful to the remote scramblers, the max_comp_time parameter should take network delay into consideration in addition to the time required to compu... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7 EMMG/PDG(MUX protocol) | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1 State diagram | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.1 Channel state machine | This clause presents the channel state machine, which defines the sequence of channel-level messages that shall be used to establish and maintain one channel on one TCP connection. The channel state machine is found in figure 6. Each state found in this state machine is defined in clauses 7.1.1.1 to 7.1.1.4. Channel No... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.1.1 Channel Not Open | This state represents the initialization of the channel state machine. At this point, a TCP connection is assumed to be established and the channel has either not been initialized, or has been closed. The EMMG initializes a channel by sending a channel_setup message to the MUX on the other end of the channel. Channel_s... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.1.2 Channel Setting Up | From this state, the MUX shall respond with either a channel_status or a channel_error message. The channel_status message acknowledges successful channel establishment, and that the channel is open. Transmission and receipt of channel_status move the state machine to the Channel Open state. The channel_error message a... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.1.3 Channel Open | This state represents the steady-state operation of the channel state machine. As long as the channel is open and error-free, streams may be opened, used and closed, per the stream state machine defined in clause 7.1.2: the stream state machine defines the stream-level and data-level messages that can be sent on a stre... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.1.4 Channel In Error | This temporary and short-lived state is used only to represent the fact that the MUX has encountered and reported an unrecoverable channel error. The EMMG shall close the channel. The EMMG sends a channel_close message to the MUX. Transmission and receipt of channel_close move the state machine to the Channel Not Open ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.2 Stream state machine | The head-end can establish one or more streams within a channel. This clause presents the stream state machine, which defines the sequence of stream-level messages that shall be used to establish, maintain and use a single stream within a channel. Streams may be established in any order (within a given channel, or glob... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.2.1 Stream Not Open | This state represents the initialization of the stream state machine. At this point, the stream has either not been initialized, or has been closed. The channel in which the stream is found shall be in the Channel Open state in order to proceed. The EMMG initializes a stream by sending a stream_setup message to the MUX... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.2.2 Stream Setting Up | From this temporary and short-lived state, the MUX shall respond with either a stream_status or a stream_error message. The stream_status message acknowledges successful stream establishment, and that the stream is open. Transmission and receipt of stream_status move the state machine to the Stream Open state. The stre... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.2.3 Stream Open | The stream is open and operational. Seven kinds of stream-level messages can be sent while in Stream Open state: • The EMMG sends a data_provision message to the MUX. This message is not acknowledged by the MUX. This message can be sent in the current stream on the same TCP connection or over an UDP link. • The EMMG ma... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.2.4 Stream In Error | This temporary and short-lived state is used only to represent the fact that the EMMG or the MUX has encountered and reported an unrecoverable stream error. The EMMG sends a stream_close_request message to the MUX. Transmission and receipt of stream_close_request move the state machine to the Stream Closing state. ETSI... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.2.5 Stream Closing | This temporary and short-lived state is used only to represent the fact that the EMMG has requested closure of the stream. The MUX sends a stream_close_response message to the EMMG, to confirm closure of the stream. Transmission and receipt of stream_close_response move the state machine to the Stream Not Open state. T... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.1.3 Summary of messages permissible in each state | Table 2 provides a listing of the channel-level and stream-level messages that may be generated in each of the states of both state machines. Table 2: message/state cross-reference for the EMMG ⇔ ⇔ ⇔ ⇔ MUX state machines Channel states Stream states (if Channel Open) Messages Not open Setting up Open In error Not open ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.2 Datagram insertion timing | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.2.1 Bandwidth definition | The EMMG/PDG protocol includes a bandwidth negotiation mechanism between the CAS and the head-end (see TS 103 197 [6], clause 6.2.1.4). According to this mechanism, on CAS request or on its own initiative, the head- end allocates the bandwidth. The bandwidth parameter is given in kbit/s (see TS 103 197 [6], clause 6.2.... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.2.2 EMM/Private Data datagram insertion | When it receives a data_provision message the Mux shall insert the datagrams in the TS according to the following rules: • For the same stream datagrams shall be inserted in TS in the order of their arrival at the Mux. • Processing of content datagrams in the Mux can introduce a constant delay between their arrival at ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.3 UDP provision without TCP control layer | According to TS 103 197 [6], when EMMG/PDG datagram provision is performed over UDP, the TCP control layer is mandatory between each MUX and the EMMG/PDG. In particular, a MUX is not allowed to process any datagrams received when a valid TCP control layer connection was not previously established with the EMMG/PDG whos... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 7.4 Datagram packetization | Datagram packetization shall comply with packetization rules defined in relevant MPEG2 and DVB standards. When multiple EMM/PD sections are sent by the EMMG/PDG in a single data_provision message (i.e. in section format) the MUX shall use as many TS packets and shall pack as many sections into each TS packet as possibl... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.1 C(P)SIG protocol profiles | The C(P)SIG protocol allows a CAS for providing descriptors to a head-end. The CAS is responsible for deciding whether a descriptor has to be inserted or deleted, for defining what this descriptor is, for indicating where and when this descriptor has to be inserted. The head-end is responsible for inserting the descrip... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2 Low-LEVEL profile definition | In this low-level profile: • only CA_descriptors for ECM in PMT and for EMM in CAT are addressed by a CAS and by a head-end; • only the connection-oriented protocol is supported; • only CPSIG and PSIG functional boxes are implemented. |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.1 CA-descriptor for ECM streams | In the low-level profile two transaction types are used: • trigger transaction type: the CAS is warned about the existence of ECM streams, about access condition change and about PID change (ECM setup, ECM closure, AC Change, PID Change); • descriptor Insertion transaction type: the CAS provides the head-end with CA-de... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.1.1 Messages | The following messages in TS 103 197 [6], clause 8.3 are not used: • table_request, table_response for Table Provisioning transaction type (see TS 103 197 [6], clause 8.2.4); • stream_service_change for Service Change transaction type (see TS 103 197 [6], clause 8.2.6); • PID_provision_request, PID_provision_response f... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.1.2 Trigger transaction type (see TS 103 197 [6], clause 8.2.3) | ECM stream setup, ECM stream closure, flow PID change, access criteria change triggers are used, corresponding to the following values of trigger types: From Table 30 of TS 103 197 [6]: Trigger types trigger cause trigger_list bit # trigger type ECM stream set up 2 0x00000004 access criteria change 3 0x00000008 ECM str... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.1.3 Descriptor Insertion transaction type (see TS 103 197 [6], clause 8.2.5) | The descriptor Insertion transaction type is limited as follows: • only PMT 1st loop and PMT 2nd loop are addressed: in table 32 of TS 103 197 [6] only location_id values 0x02 and 0x03 are used; • only CA_Descriptors are provided/inserted (no private_data_specifier parameter in TS 103 197 [6], clause 8.3.4.14); • both ... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.2 CA-descriptor for EMM streams | In the low-level profile three transaction types are used: • trigger transaction type: the CAS is warned about PID change; • flow PID Provisioning transaction type: the CAS requests for the PID allocated to an EMM flow; • descriptor Insertion transaction type: the CAS provides the head-end with CA-descriptors for CAT. |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.2.1 Messages | In TS 103 197 [6], clause 8.3 the following messages are not used: • table_request, table_response for Table Provisioning transaction type (see TS 103 197 [6], clause 8.2.4); • stream_service_change for Service Change transaction type (see TS 103 197 [6], clause 8.2.6). |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.2.2 Trigger transaction type (see TS 103 197 [6], clause 8.2.3) | Only flow PID change trigger is used. Accordingly only the following value of trigger type is used: From Table 30 of TS 103 197 [6]: Trigger types trigger cause trigger_list bit # trigger type flow PID change 5 0x00000020 In trigger message (see TS 103 197 [6], clause 8.3.4.11), the parameter table becomes: Parameter N... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.2.3 Descriptor Insertion transaction type (see TS 103 197 [6], clause 8.2.5) | The descriptor Insertion transaction type is limited as follows: • only CAT is addressed: in table 32 of TS 103 197 [6] only location_id value 0x01 is used; • only CA_Descriptors are provided/inserted (no private_data_specifier parameter in TS 103 197 [6], clause 8.3.4.14); • both values of CA_descriptor_insertion_mode... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.2.2.4 Flow PID Provisioning transaction type (see TS 103 197 [6], clause 8.2.7) | The flow_type shall be 0x00 for EMM (see TS 103 197 [6], clauses 8.3.4.16 and 8.3.4.17). |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 8.3 High-level profile definition | In this high-level profile, all features of the C(P)SIG protocol as described in the specification TS 103 197[6] are available. |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 9 SIMF based protocols - Role of NMS | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 9.1 MIB use for monitoring only | The SIM module (see TS 103 197 [6], clause 7.3) is defined to allow a NMS for configuring and monitoring a CAS device considering the Simulcrypt specific parameters. One can meet real operational cases where a CAS device (ECMG, EMMG, CPSIG) is directly configured by the CAS provider independently from any NMS, but wher... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 10 Error management | |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 10.1 Error processing in all connection-oriented protocols | Some error processing are described in TS 103 197 [6], the others are recommended below. Error case Condition Processing "unknown command" See message_type definition in TS 103 197 [6], clause 4.4.1 A message_type value is not defined in the protocol. A message_type value use does not comply with the state diagram of t... |
52635238ed0034b86d0c8db6cb063ce2 | 102 035 | 10.2 Specific inconsistencies in ECMG protocol | ECM_id parameter value in a stream_status message is different from the one given in the stream_setup message for the same stream_id (V2 only). In a channel_status message the parameter values relative to the ECMG are not the same as those given by the ECMG in the channel_status message as response to the channel_setup... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.