hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.5.5 Application protocols | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.5.5.1 CoAP over UDP Protocol | The SSP may support CoAP over UDP as defined in IETF RFC 7252 [24] using the mechanism described in the clauses above. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6 CRON service support | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.1 Overview | This clause defines a mechanism that allows an SSP host to register a timer in a CRON service in order to receive a notification (i.e. event) at a given time and date in the future. Figure 10.6 illustrates a valid platform supporting the CRON service. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 106 Release 17 CRON Applica... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.2 Presentation layer | The CRON service gate and the CRON application gates implements an ASN.1 presentation layer using the following definitions. -- ASN1START /* CRON service: definitions*/ CRON-ID ::= INTEGER (0..255) -- ASN1STOP |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3 CRON service gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.1 Overview | The CRON service gate provides access to a CRON service that manages the notification at a given date and time. The CRON service gate is in charge of: • the registration of a timer containing the time and date information for a notification requested by the SSP Application; • sending a notification (i.e. event) to the ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.2 Commands | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.2.1 List of commands | The CRON service gate supports the following commands. -- ASN1START /* CRON Service: commands */ CRON-SERVICE-GATE-Commands ::= [APPLICATION 2] CHOICE ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 107 Release 17 { aCRON-REQUEST-TIMER-Command CRON-REQUEST-TIMER-Command, aCRON-READ-DATE-Command CRON-READ-DATE-TIME-Command, aC... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.2.2 CRON-REQUEST-TIMER-Command | With the command CRON-REQUEST-TIMER-Command, an SSP Application within the SSP host requests the CRON service to create a timer, in order to be notified when it expires. The initial notification is sent either at an absolute time and date, or after a certain amount of time from the CRON-REQUEST-TIMER-Command. -- ASN1ST... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.2.3 CRON-READ-DATE-TIME-Command | With the command CRON-READ-DATE-TIME-Command a CRON application gate may request to retrieve the UTCTime of the request. -- ASN1START CRON-READ-DATE-TIME-Command ::= [PRIVATE 17] SEQUENCE { } -- ASN1STOP This command has no parameters. When successful the CRON Service shall respond with eCRON-OK with the following para... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.2.4 CRON-KILL-TIMER-Command | With the command CRON-KILL-TIMER-Command a CRON application gate may request to kill a timer previously registered in the CRON service. -- ASN1START CRON-KILL-TIMER-Command ::= [PRIVATE 18] SEQUENCE { aCRON-ID CRON-ID -- CRON id } -- ASN1STOP This command has the following parameters: • aCRON-ID: identifier of the time... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.2.5 CRON-KILL-ALL-TIMERS-Command | With the command CRON-KILL-ALL-TIMERS-Command a CRON application gate may request to kill all timers registered by an SSP host. -- ASN1START CRON-KILL-ALL-TIMERS-Command ::= [PRIVATE 19] SEQUENCE { } -- ASN1STOP This command has no parameters. When successful the CRON application gate shall respond with eCRON-OK with n... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.3 Responses | The gate supports the responses defined as follows. -- ASN1START /* CRON Service: responses */ CRON-SERVICE-GATE-Responses ::= [APPLICATION 1] CHOICE { aCRON-REQUEST-TIMER-Response CRON-REQUEST-TIMER-Response, aCRON-READ-DATE-TIME-Response CRON-READ-DATE-TIME-Response, aCRON-KILL-TIMER-Response CRON-KILL-TIMER-Response... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.3.4 Events | The gate has no dedicated events. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.4 CRON application gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.4.1 Commands | The gate has no dedicated commands. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.4.2 Responses | The gate has no dedicated responses. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.4.3 Events | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.4.3.1 List of events | The gate shall support the following events. -- ASN1START /* CRON Service: events */ CRON-APPLICATION-GATE-Events ::= [APPLICATION 0] CHOICE { aCRON-ELAPSED-TIMER-Event CRON-ELAPSED-TIMER-Event } -- ASN1STOP |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.6.4.3.2 CRON-ELAPSED-TIMER-Event | With the CRON-ELAPSED-TIMER-Event, the CRON service notifies an SSP Application that a timer has elapsed. -- ASN1START CRON-ELAPSED-TIMER-Event ::= [PRIVATE 16] SEQUENCE { aCRON-ID CRON-ID -- CRON id } -- ASN1STOP This event has the following parameters: • aCRON-ID: it is the identifier of the timer that has elapsed. E... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.7 Contactless related applications support | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.7.1 Introduction | This clause describes the emulation of an HCI host from an SSP host by using the SCL. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.7.2 HCP tunnelling over SCL | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.7.2.1 Overview | This clause defines the gates for supporting the ETSI TS 102 622 [14] HCP tunnelling over SCL. A SCL pipe session allows the tunnelling of HCP packets as defined in ETSI TS 102 622 [14] to/from HCI host controller as defined in ETSI TS 102 622 [14]. Figure 10.7 illustrates a platform supporting this gate. Figure 10.7: ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.7.2.2 SCL HCI service gate | The SCL HCI service gate provides access to a SCL HCI fragmentation and reassembly service that manages the transfer of HCP packets as defined in ETSI TS 102 622 [14] from/to a CLF compliant with the ETSI TS 102 622 [14]. The SCL HCI Service shall embed the HCP packet from the HCI Host Controller in SCL message fragmen... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.7.2.3 SCL HCI application gate | The SCL HCI application gate provides access to a SCL HCI application that emulates an HCI host as defined in ETSI TS 102 622 [14]. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 112 Release 17 The SCL HCI application shall reassembly the HCP packet as defined in ETSI TS 102 622 [14] from the message fragments of SCL packets... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8 Card Application Toolkit (CAT) over SCL | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.1 Overview | This clause defines the gates for supporting the commands and responses corresponding to Card Application Toolkit defined in ETSI TS 102 223 [6] over SCL protocol. Figure 10.8 illustrates a platform supporting this gate. The concept of envelope commands, envelope responses, proactive commands and terminal responses is ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.2 Structure of Card Application Toolkit (CAT) communications | Figure 10.9: Data objects CAT commands and responses are sent over the SCL pipe as BER-TLV data objects. The tag of a BER-TLV is a constant value, length one byte, indicating it is a CAT command. The length is coded onto 1, 2 or 3 bytes according to ETSI TS 101 220 [34], clause 7.1.2. Table 10.15 details this coding. E... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3 CAT application gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.1 Overview | This clause defines the events that the CAT application gate supports. The events defined in the following clauses shall be sent to this gate. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.2 Commands | The Gate has no dedicated commands. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.3 Responses | The Gate has no dedicated responses. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.4 Events | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.4.1 Supported events | The CAT application gate supports the events listed in table 10.16. The events are described in the following clauses. The states in which each event can be sent are defined in clause 10.8.5. Table 10.16: Supported events Value Event '10' EVT_ENVELOPE_CMD '11' EVT_TERMINAL_RESPONSE |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.4.2 EVT_ENVELOPE_CMD | This event shall be used by the host outside the SSP in order to send an envelope command (as defined in ETSI TS 102 223 [6]) to the CAT application gate. This event has the following parameter. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 114 Release 17 Table 10.17 Description Length Envelope command N The contents of the... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.4.3 EVT_TERMINAL_RESPONSE | This event shall be used by the host outside the SSP in order to send a terminal response (as defined in ETSI TS 102 223 [6]) to the CAT application gate. This is a response to EVT_PROACTIVE_CMD sent by the CAT application gate. This event has the following parameter. Table 10.18 Description Length Terminal response N ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.3.5 Registry | The gate has no registry entry. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4 CAT service gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.1 Overview | This clause defines the events that a CAT service gate supports. The CAT service gate may accept only an implementation specific maximum concurrent number of pipes from other SCL hosts. The events defined in the following clauses shall be sent to this gate. The CAT service gate URN supports the syntax as defined in cla... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.2 Commands | The gate has no dedicated commands. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.3 Responses | The gate has no dedicated responses. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.4 Events | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.4.1 Supported events | The CAT service gate supports the events listed in table 10.19. The events are described in the following clauses. The states in which each event can be sent are defined in clause 10.8.5. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 115 Release 17 Table 10.19: Supported events Value Event '10' EVT_PROACTIVE_CMD '11' EVT_EN... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.4.2 EVT_PROACTIVE_CMD | This event shall be used by the SSP host in order to send a proactive command (as defined in ETSI TS 102 223 [6]) to the CAT service gate. This event has the following parameter. Table 10.20 Description Length Proactive command N The contents of the parameter are as defined in ETSI TS 102 223 [6], clause 6.6, with the ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.4.3 EVT_ENVELOPE_RSP | This event shall be used by the SSP host in order to send an envelope response to the CAT service gate. This is a response to EVT_ENVELOPE_CMD sent by CAT service gate. This event has the following parameter. Table 10.21 Description Length Envelope response N The contents of the above parameter shall contain an optiona... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.4.5 Registry | The gate has no registry entry. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.8.5 State diagram for the CAT application gate | The states of the CAT application gate are: • TK_ST_INIT: state of the gate when an open pipe exists to the gate but Capability Exchange indicates no terminal support for Card Application Toolkit. • TK_ST_IDLE: state of the gate when no Toolkit commands are being processed. • TK_ST_PCMD: state of the gate when one or m... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9 Access control protocol | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.1 Introduction | The accessor authentication service allows authenticating an accessor to access SSP resources. The SSP shall have a dedicated accessor authentication service gate for each accessor. The accessor authentication service gate is automatically created at the creation of the accessor. The identifier of the gate has the same... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.2 Presentation layer | The accessor authentication control service gate and the accessor authentication control application gate implement an ASN.1 presentation layer using the definitions in clause 6.13.5. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.3 Accessor authentication service gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.3.1 Overview | An accessor authentication application may access to the accessor authentication service via a pipe session between a accessor authentication application gate and a accessor authentication service gate. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 118 Release 17 |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.3.2 Commands | The accessor authentication control service gate supports the following commands. -- ASN1START AAS-SERVICE-GATE-Commands ::= [APPLICATION 2] CHOICE { aAAS-OP-GET-CAPABILITIES-Service-Command AAS-OP-GET-CAPABILITIES-Service-Command, aAAS-ADMIN-CREATE-ACCESSOR-Service-Command AAS-ADMIN-CREATE-ACCESSOR-Service-Command, aA... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.3.3 Responses | The gate shall support the responses defined as follows. -- ASN1START AAS-SERVICE-GATE-Responses ::= [APPLICATION 1] CHOICE { aAAS-OP-GET-CAPABILITIES-Service-Response AAS-OP-GET-CAPABILITIES-Service-Response, aAAS-ADMIN-CREATE-ACCESSOR-Service-Response AAS-ADMIN-CREATE-ACCESSOR-Service-Response, aAAS-ADMIN-UPDATE-ACCE... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.3.4 Events | The gate has no dedicated events. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.4 Accessor authentication application gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.4.1 Overview | The accessor authentication application gate provides access to authenticate an accessor using the accessor authentication service gate. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.4.2 Commands | The gate has no dedicated commands. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.4.3 Responses | The gate has no dedicated responses. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.9.4.4 Events | The gate has no dedicated events. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 119 Release 17 |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 11 SSP classes | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 11.1 Overview | Multiple classes of SSP are defined, based on the form factor and hardware architecture, the communication protocol and other specific characteristics. Specific requirements for each SSP class are described in the corresponding specification, as defined in table 11.1. Table 11.1: List of SSP classes Class Description S... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) for the TTCN-3 conformance test suite, as defined in ETSI ES 203 790 [1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 103 663-2 [8]. The objective of the present document is to provide a basis for con... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 2 References | |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 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... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 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... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 3 Definition of terms, symbols and abbreviations | |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [7], ETSI ES 203 790 [1] (TTCN-3) and the following apply: Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any partic... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 3.2 Symbols | Void. |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASCII American Standard Code for Information Interchange ATM Abstract Test Method ATS Abstract Test Suite ETS Executable Test Suite ICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information fo... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 4 Abstract Test Method (ATM) | This clause describes the ATM used to test the conformance of Object Oriented TTCN-3 tool implementations as described in ETSI ES 203 790 [1]. In the ATM, the work is performed on two levels: • The TTCN-3 tool level. In TTCN-3 conformance tests, it is the TTCN-3 tool which is under test, i.e. the IUT. However, unlike i... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5 The ATS development process | |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.1 Requirements and test purposes | For each test purpose there is a table defined in clause A.2 of ETSI TS 103 663-2 [8]. The requirements applicable to this TP are given by a reference to ETSI ES 203 790 [1]. There are no explicit formulations of requirements. |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.2 ATS structure | |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.2.1 Test case grouping | The ATS structure defined in table 1 is based on the structuring of Test Purposes in clause A.2 of ETSI TS 103 663-2 [8]. The group names in columns 1 to 3 of table 1 are those assigned in the ATS; they are based on the names provided in clause A.2 of ETSI TS 103 663-2 [8], but use the naming conventions defined for th... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: <"TC">"_"<Group index>"_"<TC number> where: a) double quotes (") are used to enclose literal strings; b) <Group index> containing positive and negative syntactic and semantic test, refers to ETSI ES 203 790 [1] clause numbers and names; c) <TC number> ... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.3 ATS specification framework | |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.3.1 Use of TTCN-3 | |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.3.1.1 General | TTCN-3, as defined in ETSI ES 203 790 [1], is used as the ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and nami... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.3.1.2 TTCN-3 naming conventions | Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. ETSI ETSI TS 103 663-3 V1.3.1 (2022-06) 11 The naming conventions applied to Refer... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.3.1.3 TTCN-3 comment tags | Any TTCN-3 definition in the Test Suite Repository or Library should contain embedded comment tags, according to ETSI ES 201 873-10 [2]. These comment tags can be used by tools to extract information from the TTCN-3 code to create, for example, a HTML-based reference documentation. Comment tags which cover one or more ... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 5.4 ATS archive | Annex A contains the ATS archive (zip file expanding to text files with TTCN-3 code). |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 6 PIXIT conformance | A test realizer, producing an executable test suite for the Abstract Test Suite (ATS) specification, is required, as specified in ISO/IEC 9646-4 [5], to produce an augmented partial PIXIT pro forma conformant with this partial PIXIT pro forma specification. An augmented partial PIXIT pro forma which conforms to this pa... |
ca14533a3b968c74fd0b111c5dd073a9 | 103 663-3 | 7 ATS conformance | The test realizer, producing a Means Of Testing (MOT) and Executable Test Suite (ETS) for the present document, shall comply with the requirements of ISO/IEC 9646-4 [5]. In particular, these concern the realization of an Executable Test Suite (ETS) based on each ATS. The test realizer shall provide a statement of confo... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 1 Scope | The scope of the present document is to define the generalized Radio Programming Interface (gRPI) for radio equipment reconfiguration. The work is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI TS 103 641 [1] and on the radio reconfiguration related architecture for ... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 2 References | |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 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... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 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... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 3 Definition of terms, symbols and abbreviations | |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 3.1 Terms | For the purposes of the present document, the following terms apply: Abstract Processing Element (APE): abstracts computational resource that executes any computations downloaded from Radio Library NOTE: APE is connected with input and output DOs. APE is reactive. Any computations are started if all input DOs are fille... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 3.2 Symbols | Void. |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AOT Ahead-Of-Time APE Abstract Processing Element ASF Abstract Switch Fabric CC Configcodes Counter CSL Communication Services Layer CU Control Unit DO Data Object eRVM elementary RVM eSFB elementary SFB FB Functional Block FBRI FB Reusability... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 4 Introduction | A reconfigurable RE is capable of running multiple radios simultaneously, changing the set of radios by loading new Radio Application Packages (RAP) and setting their parameters. All Radio Applications (RAs) are called Unified Radio Applications (URAs) when they exhibit a common behaviour from the reconfigurable RE's p... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 5 System Requirement Mapping | The Radio Programming Interface and its related components described in the present document shall support the system requirements shown in table 5.1 referring to clause 6 of ETSI TS 103 641 [1]. This is achieved by introducing the entities/components/units given in the 1st column of table 5.1. Table 5.1: Mapping of Ra... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6 Radio Virtual Machine specification | |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.1 Concept of RVM | As introduced in ETSI TS 103 648 [i.2], the Radio Virtual Machine (RVM) is an Abstract Machine which is capable of executing Configcodes and it is independent of the hardware. The implementation of a RVM is target Radio Computer specific and it shall have access to the Back-end Compiler (on the platform itself or exter... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.2 Elementary RVM (eRVM) | This clause describes the eRVM which shall consist of components of Basic Operations, Program memory, Control Unit (CU), Abstract Switch Fabric (ASF) as well as APEs and DOs, of which the definitions are as follows. eRVM shall not contain another eRVM or RVM. • Basic Operations shall include operators either provided: ... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.3 RVM Hierarchy | Figure 6.6 illustrates RVM hierarchy which shall consist of APEs, DOs, Basic Operations, Program memory, CU, ASF and eRVMs/RVMs. Note that RVM might contain another eRVM(s)/RVM(s). Each eRVM/RVM in this case functions like an APE. Similarly to the case of figure 6.2, the CU in figure 6.6 connects the DO(s) to the corre... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.