hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.3 Parameter_type values | Table 48 defines the parameter_type values used by the interface (P)SIG ⇔ MUX. The nature of each parameter is described in the following section. Table 48: Parameter_type values for (P)SIG ⇔ MUX interface Parameter_type Value Parameter type Units Length (bytes) 0x0000 DVB Reserved 0x0001 (P)SIG_type uimsbf 1 0x0002 ch... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.4 Parameter semantics | activation_time: This integer specifies the exact time when the message shall be executed by the MUX. This value is in coordinated universal time (UTC) format i.e.: Year MSB LSB Month Day Hour Minute Second Hundredth of seconds 1byte 1byte 1 byte 1 byte 1 byte 1 byte 1 byte 1 byte ETSI ETSI TS 103 197 V1.5.1 (2008-10) ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.5 Channel specific Messages | 9.5.1 Channel_setup message: (P)SIG ⇒ MUX Parameter Number of instances in message channel_ID 1 transport_stream_ID 1 network_ID 1 (P)SIG_type 1 interface_mode_configuration 1 The channel_setup message (message_type = 0x0411) is sent by the (P)SIG to set up a channel once the TCP connection has been established. It sha... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.6 Stream specific messages for both models | 9.6.1 stream_setup message: (P)SIG ⇒ MUX Parameter Number of instances in message channel_ID 1 stream_ID 1 packet_ID 1 ASI_input_packet_ID 0 or 1 initial_bandwidth 0 or 1 The stream_setup message (message_type = 0x0421) is sent by the (P)SIG to set-up a stream once the Channel has been established. The ASI_input_packet... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 9.9 Error status | NOTE: TCP connection level errors are beyond the scope of the present document. Only channel, stream and application level errors are specified. These errors occur during the life time of a TCP connection. There are two different error messages on these interfaces. The channel_error message for channel wide errors and ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.1 Overview | This clause defines how the Event Information Scheduler (EIS) shall communicate with the Simulcrypt Synchronizer (SCS) to provide Scrambling Control Group (SCG) definitions and access criteria transitions knowing that the SCGs of an SCS shall be configured by one and only one EIS. The EIS has many functions, one of whi... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2 Interface principles | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.1 Channel specific messages | This interface shall support the following channel messages: • channel_setup; • channel_test; • channel_status; • channel_close; • channel_reset; • channel_error. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.2 Scrambling Control Group (SCG) specific messages | This interface shall support the following SCG messages: • SCG_provision; • SCG_test; • SCG_status; • SCG_error; • SCG_list_request; • SCG_list_response. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 146 For this interface, the EIS is the client and the SCS is the server. The EIS has prior knowledge of the mapping between each... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.3 Channel establishment | There is always one (and only one) channel per TCP connection. Once the TCP connection is established, the EIS sends a channel_setup message to the SCS. In the case of success, the SCS replies with a channel_status message. In the case of a rejection or failure during channel set-up the SCS replies with a channel_error... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.4 Scrambling Control Group provisioning | Based on the channel_status message received from the Simulcrypt Synchronizer (SCS) during channel establishment, the EIS can provision the SCS with the proper SCG definitions. There are three modes supported by the SCS: • service level definitions; • elementary stream (component_ID) level definitions; • mix of service... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.5 Channel closure | Channel closure can occur when the channel is no longer needed or in case of error (detected by EIS or reported by SCS). This is done by means of a channel_close message sent by the EIS. Subsequently, both sides shall close the connection. Now, if the connection is broken between the EIS and the SCS, the SCS shall cons... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.6 Channel testing and status | After a channel has been established, either the EIS or the SCS may send a channel_test message to check the integrity of a channel. In response to this message the receiving component shall reply with a channel_status message or channel_error message. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 147 |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.7 Scrambling Control Group testing and status | After a channel has been established, the EIS may send a SCG_test message to check the status of a SCG. In response to this message the SCS shall reply with a SCG_status message or SCG_error message. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.8 Unexpected communication loss | Both EIS and SCS shall be able to handle an unexpected communication loss (either on the connection or channel level). Each component, when suspecting a possible communication loss, should check the communication status by sending a test message. If a status message is not received in a given time (implementation speci... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.2.9 Handling data inconsistencies | If the SCS detects an inconsistency it shall send an error message to the EIS. After receiving the error message, the EIS may close the connection. The EIS (as the client) may then re-establish the connection. 10.2.10 Error management Error processing in EIS/SCS protocol shall be performed in a similar way as described... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.3 Parameter_type values | Table 50: EIS ⇔ SCS protocol parameter_type values Parameter_type Value Parameter type Units Length (bytes) 0x0000 DVB Reserved 0x0001 EIS_channel_ID uimsbf 2 0x0002 service_flag boolean 1 0x0003 component_flag boolean 1 0x0004 max_SCG uimsbf 2 0x0005 ECM_Group compoundTLV variable 0x0006 SCG_ID uimsbf 2 0x0007 SCG_ref... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.4 Parameter Semantics | AC_changed_flag: This parameter signals a change of the Access Criteria associated to one particular ECM stream. It shall be used to indicate to the SCS to use the AC_delay values from an ECMG for the first CP. access_criteria: This parameter contains CA system specific information of variable length and format, needed... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.5 Channel specific messages | Each message denotes the direction the message may be passed: • EIS⇒SCS - EIS may send this message to SCS only; • EIS⇐SCS - SCS may send this message to EIS only; • EIS⇔SCS - This message may be sent by either EIS or SCS. 10.5.1 channel_setup message: EIS ⇒ SCS Parameter Number of instances in message EIS_channel_ID 1... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.6 SCG specific messages | 10.6.1 SCG_provision message: EIS ⇒ SCS Parameter Number of instances in message EIS_channel_ID 1 SCG_ID 1 transport_stream_ID 1 network_ID 1 SCG_reference_ID 0 or 1 activation_time 0 or 1 recommended_CP_duration 0 or 1 component_ID 0 to n service_ID 0 to n ECM_Group 0 to n A SCG_provision message (message_type = 0x040... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.6.3.1 Response to a provisioning message | The following conditions apply if the SCS is responding to a SCG _provision message: • If SCG_reference_ID and no activation_time were provided in the provision message, the SCG_current_reference_ID value shall be set to the value received by the provision. The SCG_nominal_CP_duration value shall indicate the nominal C... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.6.3.2 Response to a test message | The following conditions apply if the SCS is responding to a SCG_test message: • If SCG_reference_ID exists in the current SCG, SCG_current_reference_ID shall be set to its value. The SCG_nominal_CP_duration value shall indicate the nominal CP duration allocated to this SCG. • If there is a pending SCG and it has an SC... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.6.3.3 Management of the SCG_nominal_CP_duration parameter | In the SCG_status message, via the SCG_nominal_CP_duration parameter, the SCS provides the value of the nominal crypto-period allocated to the currently valid SCG, namely the value of the crypto-period duration for the SCG which is active at the moment when either the SCG _provision message or the SCG_test message bein... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.6.7 ECM_Group: CompoundTLV | Parameter Number of instances in message ECM_ID 1 Super_CAS_ID 1 access_criteria 1 ac_changed_flag 0 or 1 The ECM_Group contains all the necessary information to generate ECMs for a particular ECM stream. ECM_ID is defined by DVB ETR 162 [i.2] and uniquely identifies an ECM stream. The combination of ECM_ID and Super_C... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 10.7 Error status | NOTE: TCP connection level errors are beyond the scope of the present document. There are two different error messages on this interface; the channel_error message and the SCG_error message. The channel_error message is used to communicate a channel-level error. The SCG_error message is returned specifically for SCG pr... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.1 Overview | In the context of a typical DVB Simulcrypt implementation, the way the access criteria management is perceived at the scheduling side is as follows: • In the commercial world: Service editors, operators, and content providers transmit some information concerning the access conditions associated to the programs that are... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.2 Scope | The present document defines the standard interface between the EIS and the ACG. It basically allows the EIS to request access criteria from the ACG for each event involving its respective CAS. The access criteria are always related to one and only one event. An event in this clause means a scheduled change of the stat... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.2.1 Role of the ACG | In the EISACG interface, the ACG takes on the role of the server. The ACG is responsible for providing the EIS with all CAS-proprietary information related to each event. This information is then transmitted by the EIS to SCS and possibly also to the (P)SIG. The ACG is specifically responsible for providing the EIS wi... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.2.2 Role of the EIS | In the EIS ACG interface, the EIS takes on the role of the client. The underlying assumption is that the EIS does not have to include any CAS specific knowledge and that it is the unique owner of the event schedule information in the head-end. The EIS is responsible for scheduling the transmission of event-related data... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3 Interface Principles | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.1 General Principles | This protocol has the following characteristics: • It is a connection-oriented TCP protocol. • The message structures in the protocol are XML-based. • An XML Schema Definition (XSD) is used for defining the protocol structure. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.2 Channel Specific Messages | This interface carries the following channel messages: • channel_setup; • channel_test; • channel_status; • channel_close; • channel_error. As previously stated, for the purpose of the EIS ACG interface the EIS is the client and the ACG is the server. The EIS has prior knowledge of the mapping between Super_CAS_ID and ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.3 Messages for Access Criteria Creation and Modification | This interface carries the following channel messages for access criteria creation and modification: • ac_request; • ac_response; • ac_ interrupt; • ac_error. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.4 Channel Establishment | There is always one (and only one) channel per TCP connection. Once the TCP connection is established the EIS sends a channel_setup message to the ACG. In case of success, the ACG replies by sending back a channel_status message. In the case of a rejection or a failure during channel setup, the ACG replies with a chann... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.5 Channel Closure | Channel closure can occur when the channel is no longer needed or in the case of an error (detected by the EIS or reported by the ACG). This is done by means of a channel_close message, which is sent by the EIS to the ACG. Subsequently, the connection shall be closed by both sides. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.6 Channel Testing and Status | Either component may send a channel_test message at any time to check the integrity of a channel. In response to this message the receiving component shall reply with either a channel_status message or a channel_error message. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.7 Unexpected Communication Loss | Both EIS and ACG shall be able to handle an unexpected communication loss (either on connection or channel level). When suspecting a possible communication loss (e.g. a 10 second silent period) each component should check the communication status by sending a test message and expecting to receive a status message. If t... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.8 Handling Data Inconsistencies | If the ACG detects an inconsistency it shall send an error message to the EIS. If the EIS receives such a message or detects an inconsistency it may close the connection. The EIS (as the client) will then (re-)establish the connection and the channel. The occurrence of a user-defined or otherwise unknown parameter_type... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.3.9 Handling Multiple AC Parameters in one AC Response | Each CAS may need to generate several distinct ECM streams for the same event, depending on the CAS vendor's implementation of different business models. The number of ECM streams required for an event managed by a specific CAS is therefore decided by the CAS. The latter communicates it to the EIS in the AC response me... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.4 Interface Structure | The ACG EIS interface has the follows high-level structure. Table 52: General Interface Structure Diagram Children msg_header EIS_message ACG_message Source <xs:element name="EIS_ACG_message"> <xs:complexType> <xs:sequence> <xs:element name="msg_header" type="message_header_type"/> <xs:choice> <xs:element name="EIS_mes... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.5 Parameter Semantics | access_criteria_struct: This is a complex parameter, which contains ACG_access_criteria, ac_id, AC_parameter(s), AC_expiration_time, and private_CA_element. The AC_response message contains one or more such parameters. Refer to clause 11.3.9 for details. ACG_access_criteria: This parameter represents an access criteria... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.6 Parameter Types | Table 55 describes the parameter type. See more detailed definition in the XML schema in annex M. Table 55: Parameter Type Definition Parameter Type Name Type access_criteria_struct access_criteria_structure_type comlex type acg_access_criteria acg_access_criteria_type xs:hexBinary acg_channel_id channel_id_type xs:uns... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.7 Parameters Substitution | The ACG uses the AC_parameters list in AC_response message to notify the EIS that it shall substitute the actual value of the parameters before sending the AC to the SCS using the SCG_provision message. The AC_parameter_tag is used by ACG to authenticate the specific parameter. Table 56 defines the AC_parameters_tags t... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.8 Channel Specific Messages | Each message denotes the direction the message may be passed: • EIS ACG: indicates EIS may send this message to ACG only; • EISACG: indicates ACG may send this message to EIS only; • EISACG: indicates this message may be sent by either EIS or ACG. 11.8.1 The channel_setup Message (EISACG) The channel_setup message i... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 11.9 Messages of Access Criteria Creation and Modification | 11.9.1 The AC_request Message (EISACG) The AC_request message is sent from the EIS to ACG to provide the ACG with the commercial_event_information parameter that will result in the generation of the ACG_access_criteria_struct(s). See clause 11.3.11. The commercial_event_information parameter can be different for each ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.1 Overview | The present document presents an interface between the MUXCONFIG component and any other Simulcrypt component (SIMCOMP) wishing to transmit data to a MUX for insertion in the Transport Stream generated by that MUX. The purpose of the present document is to define the required interface for allowing various SIMCOMPs to ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2 Interface Principles | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.1 System Diagram | The diagram below shows the interactions between the MUXCONFIG, and various other Simulcrypt components like the EIS, the PSIG and the EMMG. The SIMCOMP and the MUXCONFIG communicate via the TCP/IP connection. Figure 25: System Diagram for SIMCOMP MUXCONFIG In the communication between the SIMCOMP and MUXCONFIG, the MU... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.2 Data Communications and Message Format | All messages exchanged between the SIMCOMP and the MUXCONFIG share a common general format as detailed in clause 4.4.2. The messages are encoded using XML over a TCP connection. The XML Schema Definition for this protocol is described in annex L. Each message_data section: begins with a <message> tag. Under each messag... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.3 Message Groups | The SIMCOMPMUXCONFIG interface has two different message sub-groups. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.3.1 Communication channel messages | This group of messages help in setting up and managing a TCP communication channel between SIMCOMP and MUXCONFIG. It also allows for polling of the communication status between the two types of components. Table 70: Communication Channel Messages ID Message name Interface Purpose 1 channel_setup SIMCOMP MUXCONFIG The... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.3.2 Transport resource mapping messages | This group of interface messages enables any SIMCOMP component to obtain the physical device to transport mapping and get event updates for transports that move on to a different physical device within MUXCONFIG. The physical properties of the multiplexer can be different for each SIMCOMP or protocol type. ETSI ETSI TS... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.4 Channel Establishment | For the SIMCOMP and the MUXCONFIG to communicate, SIMCOMP will open a TCP/IP connection on a pre-defined socket, send a request and receive a response. The MUXCONFIG can also send asynchronous messages to SIMCOMP for redundancy replacement and channel test. The initial communication begins with the MUXCONFIG listening ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.5 Timeout and Retry | The SIMCOMP shall be able to handle an unexpected communication loss (either on the connection, channel or message level). Each component, when suspecting a possible communication loss should check the communication status by sending a test message and expect to receive a status message. If the status message is not re... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.6 Channel closure | Channel closure can occur when the channel is no longer needed or in case of error. This is done by means of a channel_close message sent by either the SIMCOMP or the MUXCONFIG. Subsequently, both sides shall close the connection. If the channel is closed or if the connection is broken, current associations ((transport... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.7 Channel testing and status | After a channel has been established, either the SIMCOMP or the MUXCONFIG may send a channel_test message to check the integrity of a channel. In response to this message the receiving component shall reply with a channel_status message or channel_error message. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.2.8 Handling data inconsistencies | If the MUXCONFIG or SIMCOMP detects an inconsistency it shall send an error message to the other party. After receiving the error message, the SIMCOMP may close the connection. The SIMCOMP (as the client) may then re-establish the connection. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.3 Parameter Semantics | channel_id: This parameter shall uniquely identify the TCP connection between the SIMCOMP and the MUXCONFIG. The channel_id is a numerical identifier for the channel. The channel_id is a unique number and must be agreed for each SIMCOMP so that any overlap or duplication is avoided. client_id: This parameter shall uniq... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.4 Interface Structure | The root element for all messages on the SIMCOMP MUXCONFIG interface is the message element. Each message element may contain one message specific child element. The message specific child elements are described in clauses 12.5 and 12.6. The XML Schema Definition for this protocol is described in annex L. Table 74: T... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.5 Channel Specific Messages | 12.5.1 The channel_setup message (SIMCOMP MUXCONFIG) The channel_setup message is sent by the SIMCOMP to the MUXCONFIG in order to set up a channel once the TCP connection has been established. It contains the channel_id and the protocol_version. The SIMCOMP channel_id will uniquely identify this connection in the MU... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 12.6 Transport Resource Mapping Messages | 12.6.1 The TS_resource_discover message (SIMCOMP MUXCONFIG) The SIMCOMP sends this message to MUXCONFIG to obtain the physical to logical mapping for all the transports and protocols that the MUXCONFIG is currently managing. This should be the first message after successful connection setup that the SIMCOMP will send... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13 Timing and Play-out Issues | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13.1 Timing issues | In all systems there is a crypto-period when data is scrambled with a particular Control Word. For STBs to regenerate the CW in time, the ECM play-out has to be correctly synchronized with this CP. To accommodate different synchronization approaches, the SCS will be responsible for requesting enough CWs and ECM packets... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13.2 Delay Start | δ start > 0 δ stop > 0 start = stop δ start < 0 δ stop < 0 start = stop CW (2) CW (3) ECM (2) ECM (3) ECM Gen A ECM (2) ECM (1) ECM (2) CP (0) CP (1) ECM (1) ECM (2) CW Gen ECM (1) ECM Gen B ECM tx A ECM tx B Crypto Period Figure 27: Delay_start and Delay_stop delay_start: This signed integer represents the amount of t... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13.3 Play-out Issues | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13.3.1 ECMs | When an ECMG sends an ECM_datagram (in the ECM_response message) for a particular ECM stream it implicitly means that: • the SCS shall trigger the play-out of this ECM at the time calculated with the delay start parameter; • the SCS shall stop the play-out of the previous ECM of the same stream at the same time; • in o... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13.3.2 EMMs and Private Data | The MUX should play-out EMMs/Private Datagrams in the order in which they arrive. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 13.4 Crypto-Period Realignment | If a new event starts in the middle of a crypto-period (either from a program or a change in Access Criteria), crypto-periods may need to be re-aligned. In the case when an activation time is provided in the SCG_provision message (as defined in EIS ⇔ SCS) initiating this realignment, and if the delay between the time w... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 1 Scope | The scope of the present document is to provide the definition of the Generic Autonomic Network Architecture (GANA) as an architectural reference model for autonomic networking, cognitive networking and self-management that addresses the requirements defined in ETSI TS 103 194 [1] - a compilation of example requirement... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 2 References | |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-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... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-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... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 3 Definitions, symbols and abbreviations | |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 103 194 [1] and the following apply: autonomically: by virtue of employing a control-loop (including feedback control-loop(s)) Autonomic Behaviour (AB): behaviour or action that may consist of a set of sub-behaviours or sub-actions tri... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: DE2DE_I DE Peer DE Interface of a DE DE2ME_E_I DE-to-ME Effector sub Interface of the DE-ME(s) Interface (DeMe) DeM Reference Point between an EMS/NMS and NEs DeMe Vertical Reference Point between a Node Main DE or Function level DE and its Managed ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rdGeneration Partnership Project AB Autonomic Behaviour AF Autonomic Function AFI Autonomic network engineering for the self-managing Future Internet AI Artificial Intelligence AMC Autonomic Management and Control AMC-MBTS Autonomic Mana... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.1 Snapshot of the GANA Reference Model | |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.1.1 Overview | Generic Autonomic Networking Architecture (GANA) reference model specifies the concepts and principles defining the domain of autonomic communication, autonomic networking, autonomic and cognitive management and control-all as part of the "big-picture" of Self-Management. Figure 1 presents the GANA abstraction levels f... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.1.2 Concept of GANA DE (autonomic Decision-making-Element) | The GANA model serves as a blueprint model that defines and prescribes the design and operational principles of autonomic Decision-making Elements (as "autonomic manager" components) called DEs. DEs are also called "Autonomic Functions" (AFs) and are responsible for autonomic management and adaptive control of systems ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.1.3 Concept of GANA MEs (Managed Entities) | GANA adopts the concept of a Managed Entity (ME) to mean a managed resource, instead of a managed element- a term used in traditional network management terminology and normally intended to mean only a physical Network Element (NE) and not some functional entity within a node/device such as a protocol module or a compo... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.1.4 Why call the behaviours of DEs self-* features? | The behaviours of DEs are called self-* features because humans are relieved from having to perform the traditionally manual management-oriented tasks, and software, i.e. the DEs, automate the tasks and dynamically perform the tasks based on human specified networking goals and policies, context or state changes, and e... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.1.5 Concept of Knowledge Plane (KP) in the GANA Model | The GANA Knowledge Plane (GANA KP) enables advanced management andcontrol intelligence at the Element Management (EM), Network Management (NM) and Operation and Support System (OSS) levels by interworking with them or enhancing and evolving the intelligence of the systems at these levels by way of replaceable and (re)-... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.4.2 GANA Level-1 DE (the lowest), called a "Protocol" Level DE | Protocol Level DE relates to any Managed Entity (ME) such as protocol, network service enabler, software components, and other fundamental mechanisms that may exhibit intrinsic control-loops and associated inbuilt DE Logic, as it is the case for most of today's protocols such as the routing protocol OSPF (Open Shortest... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.4.3 GANA Level-2 DE, called a "Function"-Level DE | This Function level DE manages entities in the networking resources layer of a Network Element (NE), including those that embed Protocol-level DE logics. The Function Level DEs relates to a DE for collective autonomic management and control of a group of protocols and mechanisms that are abstracted (viewed like a bundl... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.4.4 GANA Level-3 DE -called the Node-Main-DE | The Node-Main-DE orchestrates and manages DEs on the Function Level DE and also manages MEs in the networking resources layer that are not to be managed by the Function-level-DE but required to be managed on the node-level as described in ETSI GS AFI 002 [2] and in ETSI White Paper No.16 [3]. The Node-Main-DE relates t... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.4.5 GANA Level-4 DE (the highest)-called a "Network" Level-DE | The Network Level DE relates to a DE for autonomic management and control of those aspects that cover network- wide views and the management andcontrol of the GANA Nodes which embed lower levels DEs (node level DE, function level DE and MEs at the protocol level DE). The Control-Loops at this level complement lower lev... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.4.6 Implementation Guide for GANA DEs | The ETSI White Paper No.16 [3] provide insights on possible approaches to implementing the GANA and GANA DEs. NOTE 1: There is on-going work in ETSI on elaborations of the Implementation Guide for GANA and the resultant work is expected to be published in ETSI TR 103 195-3 [i.71]. Figure 4 illustrate the point that som... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.5 GANA's Network Governance Interface | On the Network Governance Interface, the human operator/network-administrator can manage the operation of the whole autonomic network by authoring, validating and submitting High-Level Network Objectives and some Configuration-Data and Models, all encapsulated together in the form of a data structure called the GANA Ne... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 4.6 Reference Points (Rfps) in GANA | In addition to defining the abovementioned GANA FBs, the GANA Reference Model also specifies Reference Points (Rfps) that shall be used between FBs of the GANA reference model. These Rfps between DEs may be either Horizontal Reference Points (HRPs) (i.e. between DEs belonging to same levels) or Vertical Reference Point... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.1 Overview | This clause provides more details on the GANA Core Concepts and Design and Operational Principles of GANA Functional Blocks that complement the descriptions provided in earlier clauses. 5.1.2 Structural Model of a Managed Entity (ME) at the GANA lowest layer (the resources layer), ME Interfaces, and Primitives/Operatio... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.1 Overview | Fundamental MEs are constituted by entities belonging at the bottom of the management hierarchy-at the fundamental resources layer where individual protocols or stacks, OSI layer 7 or TCP/IP application layer and other types of resources or managed mechanisms are hosted within a network element (NE) or in some device i... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.2 Primitives/Operations for Enabling ME Programmability | Clause 9.11.4 of ETSI GS AF I002 [2] describes aspects of enabling programmability for MEs and DEs. Programmability, as an enabler refers to the provision of "Primitives/Operations" on the "Management Interfaces" of various types of Managed Entities (e.g. protocols, stacks and networking mechanisms) to enable external ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.3 S_I sub-interface of the Management Interface: Sensory_Interface | MEs shall expose "Views" in form of sensory information to its associated DE through the "SensoryInterface" (S_I) sub interface of its Management Interface. Description: The Sensory Interface of an ME enables a manager entity (e.g. an upper DE) to retrieve sensory information concerning the ME state and events the ME e... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.5 E_I sub-interface of the Management Interface: Effector Interface | Effector operations/primitives shall be used by a DE owning the ME to enforce the decisions of the DE that need to be applied on the ME by sending messages or invoking commands supported by the effector interface of the ME that (re)- configure the ME. Commands/Operations/Primitives and parameters that may be available ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.6 SP_I Interface: Service Providing Interface | Operation/Primitives (with "parameters") that should be supported on the interface: These are defined in the TCP/IP Model or OSI Reference Model for interlayer interactions of protocols, up to the application layer entities that request for services of the layer beneath them. Usually, such an interface relates to MEs t... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.7 SR_I Interface: Service Requesting Interface | Operations/Primitives (with "parameters") that should be supported on the interface: These are defined in the TCP/IP Model or OSI Reference Model for interlayer interactions of protocols, up to the application layer entities that request for services of the layer beneath them. Usually, such an interface relates to MEs ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.2.8 Summary of Interfaces of an ME Model | NOTE: The Management Interface of an ME and the sub-interfaces of the Management Interface are enablers for ME Programmability. ETSI ETSI TS 103 195-2 V1.1.1 (2018-05) 54 Table 1: Summary of Interfaces of an ME Model Interface Sub- interface Full name of the sub- interface Caller and Callee/Consumer Primitives Referenc... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.1 Overview | Clause 9.11.1 of ETSI GS AFI 002 [2] presents the DE Model, which shows the Interface Names and what is happening on each interface, as well as the Primitives that should be supported by a particular DE Interface. A Management Interface of the DE is presented with its sub-interfaces and the Management Primitives that s... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.2 Cognition Module (CM) of a DE | This module is meant to implement cognitive algorithms of a DE, and also takes information received from the DE's MEs, other information gathered by the DE and knowledge pertaining to the DE's historical operations over various situations, so as to determine how the DE's cognitive capabilities (intelligence) should be ... |
93bd99013c96b7b8da9fb1e17a9998e9 | 103 195-2 | 5.1.3.4 Primitives/Operations for Enabling DE Programmability | Clause 9.11.4 of ETSI GS AFI 002 [2] describes aspects of enabling programmability for MEs and DEs. As described in the case of Primitives/Operations for Enabling ME Programmability, programmability (orchestration and configuration of state) also applies to DEs as "MEs" of some sort that should be orchestrated and/or c... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.