hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.3 UDP-based protocol | The EMMG/PDG UDP-based protocol is using the same message format as described in clause 6.2. Thanks to UDP functionality, it offers the unique advantage of broadcasting packets over a network and requires less network overhead; however, the EMMG/PDG UDP-based protocol does not provide additional feature to increase the... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.3.1 Interface principles | In this protocol, only the data_provision message is sent using UDP/IP; it is the same message as the one used in the TCP-based protocol described in clause 6.2.5.9. For the control part of this protocol, two methods can be used. The implementation of at least one of them is mandatory: • the first method consists of us... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.3.1.2 Channel and stream configuration messages | Except for the data_provision message, all messages described in clauses 6.2.4 and 6.2.5 can be used on a separate TCP/IP connection to manage channels and streams. If a broadcast mechanism is used to send data_provision messages, the client_id, data_stream_id and data_id parameters will be the same for all the Multipl... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.3.2 Bandwidth management | When using channel and stream configuration messages with UDP/IP broadcast data_provision messages, the same bandwidth negotiation messages need to be sent to all Multiplexers processing the EMM/private data stream: • where TCP connections are used to manage configurations, it is the responsibility of the EMMG/PDG to e... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7 Network management | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.1 SIMF overview | The Simulcrypt Integrated Management Framework (SIMF) addresses the requirements for interoperability between management components of multiple Conditional Access Systems (CASs) at a head-end. The framework does not address all of the issues relevant for a complete integrated Simulcrypt Management System. It specifies ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.1.1 Introduction to the Common Information Model (CIM) | The CIM provides a sufficiently large common denominator to ease the integration of basic management functions fault, configuration, and performance management into a head-end network manager or a conditional access system manager. Specifically, the CIM consists of the following information: 1) configuration and status... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.1.2 SIMF specialization options | The framework enables the design and implementation of a complete integrated management system by specifying the common management information in the SMIB and a management protocol. To enable maximum flexibility in choosing the most appropriate technology for individual head-ends and facilitate open-endedness the follo... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2 Common Information Model (CIM) | The Common Information Model (CIM) definition is closely tied to SNMPv2 and SNMPv2 SMI, as this is the first option for a network management system realization, which can be transformed into the second one by means of the JIDM process. The Common Information Model specification maps directly into an SNMPv2 SMI MIB and ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.1 Object Containment Hierarchy | Objects are unambiguously identified (or named) by assigning them an Object Identifier (OID). OIDs are globally unique for the entire Internet and are defined as a sequence of non-negative integers organized hierarchically similar to UNIX or DOS file system names. Each sequence element is also associated a textual name... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.2 MIB II | MIB II is a standard Internet MIB (see RFC 1213 [2]). Every SNMP agent is assumed to support MIB II. MIB-II, like its predecessor, the Internet-standard MIB, contains only essential elements. There is no need to allow individual objects to be optional. Rather, the objects are arranged into groups which are implemented ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.3 Concurrency control | Concurrency control of simultaneous updates of an agent's MIB variables by multiple managers is accomplished by using the SMIB SIM module's administrative state variables (as defined in the ITU-T Recommendation X.731 [4] standard used in TMN) and the SNMP administrative framework. An administrative state of a group of ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.4 Simulcrypt Events Module (SEM) | SEM enables managers to configure the types of events that can be generated by an agent and when those events should be transformed into asynchronous notifications (SNMP Traps) to be sent to different managers. The mechanism and information model used are based on the ITU-T Recommendations X.733 [5] and X.734 [6] stand... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.4.1 Event Group | This group consists of event configuration information defining the types of events that the agent shall generate. Table 9: CIM - SEM (P)SIG Group - Event Table Object Size/Description Object Justification Head-end/CA Manager Maximum Access Right semEventName bslbf/the unique name of the target event, EntryName (SNMP) ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.4.2 Event Forwarding Discriminator (EFD) Group | This group consists of EFD configuration information defining what types of events an EFD will transform into notifications, at what times of day it will do so, and to which managers it will send the notifications to. An EFD generates a notification if it is unlocked (administrative state), enabled (operational state) ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.4.3 Event Notification Group | This group defines three types of notifications which an agent can send to a manager. These are an alarm, a state change notification, and a value change notification. Each EFD specifies what type of notification is to be sent for an event that has occurred in the agent. The EFD also specifies the conditions under whic... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.4.4 Conformance requirements | The Simulcrypt Events Module (SEM) is optional. However if this module is implemented, table 9 summarizes the conformance requirements for management entities implementing the Simulcrypt Events Module (SEM). Table 11: CIM - SEM Conformance Requirements Common Information Model- Simulcrypt Events Module Group Management... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.5 Simulcrypt Logs Module (SLM) | SLM enables managers to configure the types of logs that can be generated by an agent. The mechanism and information model used are based on the ITU-T Recommendation X.735 [7] Log Model. The log in addition to conceptually storing the logged information determines which information is to be logged. Each log contains a ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.5.1 Log Control Group | This group defines the types of logs tables the agent is maintaining, their discriminators, the log scheduling, etc. The group consists of two tables, the Log Definition Table and the Log Control Table. The Log Definition Table (table 12) is used to define all logs in the system. Each entry consists of an slmLogDefinit... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.5.2 Logs Group | The three logs defined are defined as tables in which each event is stored as a row. The logs in the alarm log table are logs of alarm events that have passed the log control discriminator in the Log Control Table. Similarly the logs in the state change log table are logs of state changes. Logs in the object value chan... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.2.5.3 Conformance Requirements | The Simulcrypt Logs Module (SLM) is optional. However if log management is implemented the following conformance requirements hold. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 68 Table 17: CIM - SLM Conformance Requirements Management Entity Hosting or Representing an ECMG Management Entity Hosting or Representing an EMMG/ M... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.3 CAS component monitoring and configuration | Monitoring and configuration of CAS components is accomplished through the Simulcrypt Identification Module (SIM). SIM contains version information of the management software as well as Simulcrypt component identification, configuration, and status information. Its primary purpose is to provide uniform Simulcrypt compo... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.3.1 Ident Group | This group is used for software configuration management of all Simulcrypt components and includes the following objects. Table 18: CIM - Simulcrypt Identification Module Object Size/Description Object Justification Maximum Access Right simSoftwareVersion 80 bslbf/ASCII string of software version to facilitate software... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.3.2 ECM Generator Group | This group is used for configuration management and status monitoring of ECM Generators. It identifies each one of the ECM Generators by the IP Address and TCP Port Number. It associates Super_CAS_ids, ECM_channel_ids, and ECM_stream_ids with ECM Generators. It also associates status information and statistics with cha... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.3.3 EMMG/PDG Group | This group is used for management of EMM/PD Generators. It identifies each one of the EMM/PD Generators by the IP Address and TCP/UDP Port Number. It also associates client_ids, data_channel_ids, and data_stream_ids with EMM/PD Generators. It also associates status information and statistics with streams. The EMMG/PDG ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.3.4 C(P)SIG Group | This group is used if the (P)SIG Group is not implemented and the stream/channel based protocol between the Custom (P)SIG and (P)SIG is implemented. The C(P)SIG Group enables management of some aspects of the interaction between the Custom (P)SI Generators (C(P)SIG) and the (P)SI generator. It identifies each one of th... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 7.3.5 Conformance Requirements | Table 30 summarizes the conformance requirements for management entities implementing the Simulcrypt Identification Module (SIM), by group. Table 30: CIM - SIM Conformance Requirements Common Information Model - CIM Simulcrypt Identification Module Group Management Entity Hosting or Representing an ECMG Management Enti... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.1 Overview and Scope | This clause defines the interface that allows one or more CA Systems (CASs) to insert private data into standard MPEG-2 PSI and DVB SI tables that are generated by the head-end system. The following clauses detail an application protocol model for the C(P)SIG ⇔ (P)SIG interface and two implementation-oriented protocols... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.1.1 Note on commercial agreements | Certain aspects of the C(P)SIG ⇔ (P)SIG interface fall outside the scope of the present document, and shall be decided by commercial agreements. One such example is the set of non-mandatory PSI and SI tables generated by a (P)SIG. All such aspects of this interface are indicated in the text. 8.1.2 Note on the PDG ⇔ MUX... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2 Application protocol model | 8.2.1 Overview of the C(P)SIG ⇔ (P)SIG Application Protocol The C(P)SIG⇔(P)SIG Application Protocol includes and defines the following five transaction types: • Trigger Transactions: Triggers are asynchronous events from the (P)SIG to the C(P)SIG. The (P)SIG first informs the C(P)SIG about the types of triggers it supp... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2.2 Configurations and Topologies | Figure 10 illustrates the relevant components in a head-end system with a single CA System (CAS) and in a head-end system with multiple CASs. In both diagrams, the M-to-N and 1-to-N notation reflects logical associations, not process interconnections. CAS HEAD-END SYSTEM CAS C(P)SIG (s) PSIG (s) Transport M N 1 N C(P)S... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2.3 Trigger Transaction Type | The trigger is the means by which a (P)SIG component indicates to a C(P)SIG that a particular event is going to take place. DVB Simulcrypt has identified the following trigger types: • Following DVB-event; • Future DVB-event; • ECM stream setup; • Access criteria change; • ECM stream closure; • Flow PID change; • PD st... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2.4 Table Provisioning Transaction Type | The C(P)SIG communicates to the (P)SIG the following information uniquely identifying in a given transport-stream the table the C(P)SIG is requesting, according to table 33. Original network identifier and transport identifier (original_network_id and transport_stream_id as defined by DVB SI) identifying the transport ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2.5 Descriptor Insertion Transaction Type | The C(P)SIG communicates to the (P)SIG the descriptors that the C(P)SIG wants to be inserted in the PSI/SI tables of a given transport stream. This includes all the information that the (P)SIG needs to know where and when to insert the descriptors. The information depends on the type of descriptor inserted and is speci... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2.6 Service Change Transaction Type | The (P)SIG informs the C(P)SIG about a modification in service existence in a transport stream (addition of a service to a transport stream or deletion of a service from a transport stream). More sophisticated functions such as service_id change or the move of a service from one transport stream to another transport st... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.2.7 Flow PID Provisioning Transaction Type | The PID provision functionality is available only in the C(P)SIG ⇔ (P)SIG protocol. As used in this clause, the word "flow" concerns an ECM stream, an EMM stream or a private data stream in a particular transport stream. A (P)SIG can provide a C(P)SIG with the PID of a flow by one of these four ways: • by explicit requ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3 Connection-oriented protocol | This clause specifies the connection-oriented instance of the generic C(P)SIG ⇔ (P)SIG protocol defined in the clause 8.2. In such an implementation the C(P)SIG and (P)SIG processes communicate with each other via a connection-oriented protocol. 8.3.1 Overview of the C(P)SIG ⇔ (P)SIG connection-oriented protocol |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.1 Principles | In this connection-oriented protocol, the (P)SIG is the client and the C(P)SIG is the server. The (P)SIG has a prior knowledge of the mapping between Custom_CAS_id and the IP addresses and port numbers of the C(P)SIG. Once the (P)SIG has established a TCP connection with the C(P)SIG, it opens a channel (see clause 8.3.... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.2 Channels | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.2.1 Definition and types | The logical connection between a C(P)SIG and a (P)SIG is comprised of one and only one channel per CAS. There is only one channel per TCP connection. Since a channel interconnects a single C(P)SIG with a single (P)SIG, any of seven types of channels is possible; refer to the leftmost diagram in figure 12. The channel t... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.2.2 Channel establishment | The head-end is responsible for establishing all channels at system initialization time, or when a CAS is newly interfaced to the head-end. Accordingly, the head-end (and possibly the CAS) shall have prior information of the channels to be established, as well as all parameters required for connection. This channel inf... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.3 Streams | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.3.1 Definition | As described in clause 8.3.1.2, a channel connects a C(P)SIG with a (P)SIG. A channel logically connects a C(P)SIG with one or more TSs. A stream is a logical connection between a C(P)SIG and a (P)SIG, which serves a single TS. As such, a stream "belongs" to a channel. Within a channel, the relationship between stream ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.3.2 Stream establishment | The head-end is responsible for establishing all streams at system initialization time, or when a CAS is inserted to the head-end. Accordingly, the head-end (and possibly the CAS) shall have prior information of the streams to be established, as well as all parameters required for connection. This stream information is... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.5 Protocol state machines definition | This protocol is based on two state machines. The first state machine defines the transitions associated with each channel. The second state machine defines the transitions associated with each stream; this state machine is valid only for a channel in the Channel Open state. The state machines defines: • States: a tota... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.6 Channel state machine | As described in clause 8.3.1.2.2, the head-end establishes and maintains one or more channels between (P)SIG and C(P)SIG processes. This clause presents the channel state machine, which defines the sequence of channel-level messages that shall be used to establish and maintain a single channel. Channels may be establis... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.6.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 (P)SIG initializes a channel by sending a channel_setup message to the C(P)SIG on the other end of the channel. C... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.6.2 Channel Setting Up | From this state, the C(P)SIG 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 C(P)SIG also indicates, via this message, the maximum number of streams that can be supported on the new chann... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.6.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 8.3.1.7: the stream state machine defines the stream-level and data-level messages that can be sent on a st... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.6.4 Channel In Error | This temporary and short-lived state is used only to represent the fact that the C(P)SIG has encountered and reported an unrecoverable channel error. The (P)SIG shall close the channel: • The (P)SIG sends a channel_close message to the C(P)SIG. Transmission and receipt of channel_close move the state machine to the Cha... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7 Stream state machine | As described in clause 8.3.1.3.2, the head-end establishes 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 ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.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 (P)SIG initializes a stream by sending a stream_setup message to the C... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.2 Stream Setting Up | From this temporary and short-lived state, the C(P)SIG 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; • ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.3 Stream Open | The stream is open and operational, and capable of performing all operations with exception of action triggering by the (P)SIG. Thirteen kinds of stream-level messages can be sent while in Stream Open state: • the C(P)SIG sends a stream_trigger_enable_request message to enable the receipt of (P)SIG action triggers in t... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.4 Stream Trigger Enabling | This temporary and short-lived state is entered only after the C(P)SIG sends a stream_trigger_enable_request message while in the Stream Open state or in Stream Trigger Enabled state. One kind of stream-level messages can be sent while in Stream Trigger Enabling state: • The (P)SIG sends a stream_trigger_enable_respons... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.5 Stream Trigger-Enabled | This state represents the normal steady-state operation of the stream state machine. The stream is open and operational, and capable of performing all operations, including (a) action triggering by the (P)SIG, and (b) requests for CAS-specific private data insertion by the C(P)SIG. Fourteen kinds of stream-level messag... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.6 Stream In Error | This temporary and short-lived state is used only to represent the fact that the C(P)SIG has encountered and reported an unrecoverable stream error: • The (P)SIG sends a stream_close message to the C(P)SIG. Transmission and receipt of stream_close move the state machine to the Stream Not Open state. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.7.7 Stream Closing | This temporary and short-lived state is used only to represent the fact that the C(P)SIG has requested closure of the stream: • The (P)SIG sends a stream_close_response message to the C(P)SIG, to confirm closure of the stream. Transmission and receipt of stream_close_response move the state machine to the Stream Not Op... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.1.8 Summary of messages permissible in each state | Table 35 provides a listing of the channel-level and stream-level messages that may be generated in each of the states of both state machines. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 101 Table 35: Message/state cross-reference for the C(P)SIG ⇔ (P)SIG state machines State Channel (assumes Stream Not Open) Stream (assumes... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.2.2 Parameter semantics | This clause gives the semantic of the parameters and fields used in this protocol. When depending on the message context, some parameters can be completed in each message description in further clauses. • access_criteria: this parameter carries the access criteria concerning an ECM stream; • bouquet_id: this parameter ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.3 Channel-level messages | This clause defines the syntax and semantics of each channel-level message. It refers to the syntax and semantic of parameters given in clause 8.3.2; however for some parameters according to a particular message context, complementary descriptions can be given to complete or to replace descriptions given in clause 8.3.... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.4 Stream-level messages | This clause defines the syntax and semantics of each stream-level message. It refers to the syntax and semantic of parameters given in clause 8.3.2; however for some parameters according to a particular message context, complementary descriptions can be given to complete descriptions given in that clause. 8.3.4.1 strea... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.3.5 Error status and error information | NOTE: TCP connection level errors are beyond the scope of the present document. Only channel, stream and application level errors are dealt with. These errors occur during the lifetime of a TCP connection. Table 37: C(P)SIG connection-oriented protocol error values error_status value Error type 0x0000 DVB Reserved 0x00... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4 SIMF-based protocol | This clause specifies the SIMF-based implementation of the C(P)SIG ⇔ (P)SIG interface. This implementation is based on the (P)SI Object Information Group of the Simulcrypt Identification Module (SIM) and the Operations Reference Point (ORP) operations paradigm that can be used between any components within Simulcrypt (... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.1 Operations Reference Points (ORPs) | The information exchange and synchronization between any number components is accomplished through the SIMF as follows: • the component advertises information such as SI/PSI information through a Management Information Base (examples SNMPv2 SMI MIB); that is done through a software agent (e.g. SNMPv2 agent) or through ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.2.1 ECM/Event/Flow Change Triggering | The (P)SI/C(P)SI ORP facilitates ECM/Event/Flow Change Triggering as follows: 1) the (P)SIG's Event Table is configured from start-up to generate events whenever there is a new entry in any of the three Trigger tables (i.e. the ECM, and Event Trigger tables); for each type of Trigger there is a different type of event;... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.2.2 (P)SI Table Provisioning | The C(P)SIG requests (P)SI through the (P)SIG's Provisioning table. This table is just an interface to the (P)SI information within the (P)SIG or a proxy function to such information. The reply to the provisioning request contains the desired table or a part of the desired table if the table is too large to be sent in ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.2.3 (P)SI Descriptor Insertion | The C(P)SIG requests (P)SI descriptor insertion through the (P)SIG's Descriptor Insert table. That table may also be just an interface to (P)SIG's descriptor insert application. The reply to the descriptor insert request informs the C(P)SIG whether the descriptor insertion was successful. ETSI ETSI TS 103 197 V1.5.1 (2... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.2.4 Transport Stream Service Changes | The (P)SIG announces changes in services on the transport stream by changing a variable in the (P)SIG Configuration Table that contains the service identifiers of all services on the transport stream. Each C(P)SIG configures the (P)SIG's event and EFD tables so that it will receive a notification if the (P)SIG transpor... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.2.5 PID Provisioning | The C(P)SIG requests from the (P)SIG the PID value assigned by the head-end to a stream (ECM, EMM or private data) through the PID Provisioning table. That table may be also just an interface to (P)SIG's database. The stream is identified by its type, the identifier of the CA system and the CA sub-system the stream bel... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3 SIM (P)SIG Group Specification | This group consists of nine tables: • (P)SIG Information Table; • (P)SIG Configuration Table; • ECM Trigger Table; • Event Trigger Table; • Flow PID Change Trigger Table; • Descriptor Insert Table, • Descriptor Insert Descriptor Table; • Table Request Table; • PID Provisioning Table. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.1 Information Table | The first table is the (P)SIG information table. It is used by the (P)SIG to advertise its configuration, the transport streams it handles, and the services contained in all the transport streams. The table is indexed by simPsigIndex. The information consists of the following. Table 38: CIM - SIM (P)SIG Group - (P)SIG ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.2 Configuration Table | The second table is the configuration table. It is used to configure (P)SIG/C(P)SIG interaction. Each table row access is controlled by the administrative state variable and the row status variables as defined in the corresponding ITU-T and IETF standards. The table is indexed by the simPsigConfigCustCasId, the simPsig... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.3 ECM Trigger Table | The third table is the ECM Trigger table. It is used for the (P)SIG to enter ECM Triggers and for the C(P)SIG to read them. Upon entering a new entry (ECM Trigger) into this table an event is automatically generated by the (P)SIG as specified in the Events Configuration Table of the Simulcrypt Events Module (SEM). This... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.4 Flow PID Change Trigger Table | The fourth table is the Flow PID Change Trigger table. It is used for the (P)SIG to enter Flow PID Change Triggers and for the C(P)SIG to read them. Upon entering a new entry (Flow PID ChangeTrigger) into this table an event is automatically generated by the (P)SIG as specified in the Events Configuration Table of the ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.5 Event Trigger Table | The fifth table is the Event Trigger table. It is used for the (P)SIG to enter Event Triggers and for the C(P)SIG to read them. Upon entering a new entry (Event Trigger) into this table an event is automatically generated by the (P)SIG as specified in the Events Configuration Table of the Simulcrypt Events Module (SEM)... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.6 PD Trigger Table | The sixth table is the PD Trigger table. It is used for the (P)SIG to enter PD Stream Event Triggers and for the C(P)SIG to read them. Upon entering a new entry (PD Trigger) into this table an event is automatically generated by the (P)SIG as specified in the Events Configuration Table of the Simulcrypt Events Module (... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.7 Descriptor Insert Table | The sixth table is the Descriptor Insert table. It is used for the C(P)SIG to enter (P)SI descriptors and for the (P)SIG to read them. Entering of a descriptor completes the cycle which was started by EMM/ECM/Event triggering. The actual descriptors to be inserted are written into the descriptor table. The descriptor i... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.8 Descriptor Insert Descriptor Table | The seventh table is an extension to the descriptor insert table. It consists of a list of descriptors (simPsigDescInsDescriptor) to be inserted and their insertion return status (simPsigDescInsDescriptorStatus). The Descriptor Insert Descriptor Table is indexed by the index of the descriptor insert table and by its ow... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.9 Table Request Table | The eighth table is the Table Request table. It is used for the C(P)SIG to request and retrieve (P)SI tables from the (P)SIG. The table is used as an interface to the (P)SI database. Since tables retrieved may exceed the maximum message size supported by the underlying transport (i.e. SNMP) a mechanism is provided to s... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.3.10 PID Provisioning Table | The ninth table is the PID Provisioning table. It is used for the C(P)SIG to request from the (P)SIG the PID value assigned by the head-end to a stream (ECM, EMM, or private data). The stream is identified by its type, the identifier of the CA system and the CA sub-system the stream belongs to, and a unique stream numb... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 8.4.4 Conformance Requirements | Table 47 summarizes the conformance requirements for management entities implementing the Simulcrypt Identification Module (SIM), by group. Table 47: CIM - SIM (P)SIG Group - Conformance Requirements Common Information Model - CIM Simulcrypt Identification Module Group Management Entity Hosting or Representing an ECMG ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.1 Overview | The diagram in figure 17, illustrates the exact role of the (P)SIGMUX interface in the context of a Simulcrypt head-end system. In this clause, the acronym (P)SIG stands either for a PSISIG, a unique logical component generating both PSI and SI tables, or for a pair (PSIG, SIG) i.e. two distinct unique logical compone... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2 Interface principles | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.1 Description | This interface is based on a Channel/Stream model as used by the other connection-based protocols defined in the present document. The (P)SIG, as a client, connects to one MUX, the server, by establishing a channel that is associated with a particular (transport_stream_ID, original_network_ID) pair. The (P)SIG may open... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.2 Channel and Stream specific messages | The interface shall carry the following channel messages: For both models: • channel_setup; • channel_test; • channel_status; • channel_close; • channel_error. For the first model when the carousel is performed in the MUX only: • CIM_channel_reset. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 134 The interface shall carry the... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.3 Channel establishment | The (P)SIG is assumed to have a prior knowledge of the mapping between the pairs {transport_stream_Id, original_network_ID} (each identifying one particular transport stream), and the respective pairs {IP Address, Port Number} of the MUXs. Once the TCP connection is established, the (P)SIG sends a channel_setup message... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.4 Stream level protocol for the model with the carousel in the MUX | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.4.1 Stream establishment | The (P)SIG sends a stream_setup message to the MUX. This message contains in particular the value of the PID with which the sections provisioned on this stream will have to be inserted in the targeted transport stream. Two different streams are not allowed to manage the same PID value at the same time. In case of succe... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.4.2 Provision of the PSI/SI or private sections | Once the connection, channel and stream have been correctly established, the (P)SIG can send to the MUX the sections it wants to be broadcast on the particular PID associated to this stream. The sections are transmitted in CiM_stream_section_provision messages and they replace the possible previous sections broadcast o... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.4.3 Stream closure | Stream closure is always initiated by the (P)SIG. This is done by means of a stream_close_request message. A stream_close_response message indicates the stream has been closed. However, a stream closure does not mean that the broadcasting of the associated sections is interrupted. The last previously transmitted collec... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.5 Stream level protocol for the model with the carousel in the (P)SIG | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.5.1 Stream establishment | For this model, the (P)SIG also sends a stream_setup message to the MUX. In case of success the MUX replies by sending back a stream_status message. In case of a rejection or a failure the MUX replies with a stream_error message. The stream_setup message contains in particular the value of the PID, called packet_ID, wi... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.5.2 Bandwidth allocation | During stream set-up the (P)SIG shall request the bandwidth needed for that stream in the stream_setup message. The MUX will then respond with the bandwidth that has been allocated for that stream. The (P)SIG can, at a later time, request an adjustment in the bandwidth allocation. The (P)SIG/MUX protocol bandwidth is d... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.5.3 Stream closure | Stream closure is always initiated by the (P)SIG. This can occur when a PSI/SI stream is no longer needed. This is done by means of a stream_close_request message. A stream_close_response message indicates the stream has been closed. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.6 Channel closure | Channel closure can occur when the Channel is no longer needed or in case of error (detected by (P)SIG or reported by MUX). This is done by means of a channel_close message sent by the (P)SIG. Subsequently, the connection shall be closed by both sides. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.7 Channel/Stream testing and status | At any moment either component can send a channel_test/stream_test message to check the integrity of a channel/stream. In response to this message the receiving component shall reply with either a channel/stream status message or a channel/stream error message. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.8 Unexpected communication loss | Both (P)SIG and MUX shall be able to handle an unexpected communication loss (either on the connection, channel or stream level). Each component, when suspecting a possible communication loss (e.g. a 10 second silent period), should check the communication status by sending a test message and expecting to receive a sta... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.9 Handling data inconsistencies | If the MUX detects an inconsistency it shall send an error message to the (P)SIG. If the (P)SIG receives such a message or detects an inconsistency it may close the connection. The (P)SIG (as the client) will then (re-)establish the connection, channel and (if applicable) streams. The occurrence of a user defined or un... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.2.10 Error management | Error processing in PSIG/MUX protocol shall be performed in a similar way as described in TR 102 035 [i.6] for all other connection-based protocols. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.