hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.4 Data types | |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.4.1 Types and Values | The only data types for DOs shall be tokens which have some size in bits. The DOs structure is recognized by initialized APE. NOTE: As one example, full DOs can be treated an allocation of bits in memory. |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.4.2 Run-Time Data | There shall be the following Run-Time Data types: 1) CC (Configcodes Counter) register: positive 32-bit integer. 2) Constant DOs: dynamic allocation of bits existing only during task execution and initialized by some external agent. In short, this DO is related to externally provided data. 3) Intermediate DOs: dynamic ... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.5 Arithmetic | Arithmetic is not fixed but defined by operations from Basic Operations. |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.6 Exceptions | There shall be 2 types of exceptions: • Generated by DOs, see table 6.1. Table 6.1: DO Exceptions Value Semantic 00 No exception 01 Operation with size > DO size 10 Conflicting writes 11 Conflicting read-erase operations • Generated by APEs/(e)RVMs, see table 6.2. Table 6.2: APE/(e)RVM Exceptions Exception Semantic 00 ... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.7 Control, Synchronization and Execution | Control shall be data-driven only. Execution shall be done by APE in case that: • All input DOs are configured and full in case of terminal operations. • All input DOs are configured and some of them are full in case of nonterminal operations. ETSI ETSI TS 103 681-4 V1.1.1 (2020-03) 18 • APE is configured. • APE is con... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.8 Operations with Memory | In the applied model, memory is considered be flat and infinite. Its implementation is out the scope of the present document. Any RVM shall have access to the memory. DOs shall be allocated in the memory during their configuration. The memory shall allow multiple parallel read write operations. Conflicting operations s... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 6.9 RVM run-time environment | The RVM Runtime Environment (RVM RE), e.g. software based, allows to run RAs which might be Configcodes or executable codes: 1) In case of CConfigcode execution, the RVM RE comprises a RVM interpreter. 2) In case of executable codes, binary platform-specific codes are created which are executed on the target platform. ... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 7 Configcodes for RVM | |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 7.1 Introduction | This clause explains how the Configcodes are generated as a result of front-end compilation of the software Intermediate Representation (SWIR) during the design time of RA code distribution. The Configcodes are typically generated in either binary or eXtensible Markup Langugage (XML) depending on vendor's choice. |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 7.2 Configcodes generation | This clause explains how the Configcodes are generated in either binary or XML format, which is referred to as a RVM Input file in the present document. Figure 7.1 illustrates the processing steps of generating the Configcodes from corresponding SWIR. Processing of Configcodes generation shown in figure 7.1 starts from... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 7.3 Binary format for Configcodes | In this clause, the format of binary Configcodes is presented. Each task shall include one or several Configcodes. Each of them shall consist of Control Configcode, DO Configcode, APE Configcode, ASF Configcode and optionally Next Configcode Address Offset (NCAO). The field NCAO shall be augmented if NAF = 1. The binar... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 7.4 XML schema for Configcodes | In this clause, the XML schema for Configcodes is presented. Each task includes one or several Configcodes. Task configcode DOconfig APEconfig DO Virtual ASF Port APE Complex Switch IF FOR WHILE Port Port Port Port Port Port Figure 7.8: XML elements consisting of Configcodes Figure 7.8 illustrates the XML elements cons... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 8 Radio Library | |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 8.1 Introduction | The Radio Library shall include the entire set of SFBs [i.2]. The Radio Library is categorized into two kinds as follows: • Reference Radio Library shall provide normative definition of each SFB. • Native Radio Library shall provide platform-specific description of each SFB which represents the target platform hardware... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 8.2 Reference Radio Library | The Reference Radio Library shall include the information regarding each operator downloaded from the Basic Operations of RVM introduced in clause 6 in the case of front-end compilation. The operator corresponds to each SFB defined in ETSI TS 103 648 [i.2]. The Reference Radio Library shall include normative definition... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 8.3 Native Radio Library | The Native Radio Library shall include information on how each SFB in the Reference Radio Library is implemented in a target hardware platform. The information shall explicitly specify the implementation of each SFB in the Reference Radio Library using dedicated hardware accelerators and/or programmable devices provide... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 9 Loading, Linking and Initialization | RVM shall be instantiated for execution of platform-specific Configcodes obtained from the back-end compiler. The instantiation consists of three steps (following back-end compilation creating platform-specific ConfigCodes for RVM (note: in a different set-up, back-end compilation may create binary code, then no RVM pr... |
da216e15356254a6dd99b59f9d2c0e78 | 103 681-4 | 10 Compiling for RVM (Front-End Compilation) | This paragraph describes the front-end part of the compilation process related to the transformation of input source code into platform independent RVM Configcodes. There are two alternatives to obtain Configcodes: 1) RadioApp code (e.g. in C, C++, Java, etc.) is used as an input. Following parallelization (SWIR is obt... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 1 Scope | The scope of the present document is to define an information model and protocol for unified radio application interface 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 re... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 2 References | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-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... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-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... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 3 Definition of terms, symbols and abbreviations | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 3.1 Terms | For the purposes of the present document, the following terms apply: association: logical communication link to a Radio Access Network or a peer equipment NOTE 1: Typically, some control signalling is necessary to maintain the association. No user data transfer may occur with only an association present, but a data flo... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 3.2 Symbols | Void. |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One BLER BLock Error Rate CM Configuration Manager CSL Communication Services Layer FC Flow Controller gMURI generalized Multiradio Interface gRPI generalized Radio Programming Interface gRRFI generalized Reconfi... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 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... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 5 System Identification | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 5.1 Radio Computer Structure | Figure 5.1 illustrates how RCF and URA interact with each other using gURAI. ETSI ETSI TS 103 681-3 V1.1.1 (2020-03) 10 Figure 5.1: Interconnection between RCF and URA using gURAI for Reconfigurable RE As shown in figure 5.1, gURAI supports 3 kinds of services: • Radio Application Management Services - These services a... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 5.2 gURAI System Requirement Mapping | The Radio Computer components above described shall support the gURAI system requirements shown in table 5.1 and described in clause 6 of ETSI TS 103 641 [1]. Table 5.1: Mapping of Radio Computer Components to the system requirements described in ETSI TS 103 641 [1] Entity/Component/Unit System Requirements [1] Comment... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 6 Notational Tools | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 6.1 Notational Tool for Information Model Classes | In the present document, information model classes are used as defined in annex B.1 of IEEE 1900.4TM-2009 [i.3]. |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 6.2 Notational Tool for Interface Classes | Table 6.1 shows a template for defining interface classes for gURAI. Each interface class for gURAI will be defined in clause 8.5 in accordance with the template shown in table 6.1. Table 6.1: Template for defining Interface Classes Class<Class name>[(abstract class)] <Description of the class> OPERATIONS <Operation na... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 7 Information Model for Radio Computer | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 7.1 Radio Computer | Figure 7.1 shows the UML class diagram for Radio Computer classes related to gURAI which are required to support Software Reconfiguration. The diagram includes classes which are directly and indirectly related to gURAI. <<interface>> IgURAI RadioComputer -RCID: NameType RCMeasurements -listOfActiveMeasurements: ActiveM... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 7.2 Class Definitions for Information Model | Each class of Radio Computer can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of figure 7.1 which specifies the relations among all the classes of Radio Computer. Radio Computer classes defined in this way are shown in tables 7.1 to 7.20. Table 7.1: RadioComputer Class Cl... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8 Interface Definition | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.1 Interface Overview | Figure 8.1 illustrates a UML diagram for gURAI. gURAI supports 3 basic services (i.e. Radio Application Management Services, User Data Flow Services, and Multiradio Control Services) which are further detailed in clauses 8.2, 8.3 and 8.4 respectively. ETSI ETSI TS 103 681-3 V1.1.1 (2020-03) 22 <<interface>> IgURAI <<in... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.2 Radio Application Management Services | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.2.1 Overview on Radio Application Management Services | Table 8.1 describes an overview on Radio Application Management Services which are associated with RCM. Class definition and related operations are described in clause 8.5. ETSI ETSI TS 103 681-3 V1.1.1 (2020-03) 23 Table 8.1: Overview on Radio Application Management Services Radio Application Management Services Expla... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.2.2 Messages for Radio Application Management Services | The interfaces for Radio Application Management Services are used to transmit the following messages: • From RCF to URA: - Request of report discovered Peer Equipment. - Request of create/terminate association with Peer Equipment. - Request of start and stop communication with Peer Equipment. • From URA to RCF: - Confi... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.3 User Data Flow Services | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.3.1 Overview on User Data Flow Services | Table 8.2 describes an overview on User Data Flow Services which are associated with FC. Class definition and related operations are described in clause 8.5. Table 8.2: Overview on User Data Flow Services User Data Flow Services Explanation Data flow control In sending or receiving user data, there might be some confli... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.3.2 Messages for User Data Flow Services | The interfaces for User Data Flow Services are used to transmit the following messages: • From RCF to URA: - Request of user data transfer. NOTE 1: Request of user data transfer initiates TX operation in URA. - TX Information related to URA. NOTE 2: Examples of TX Information may include signal bandwidth, carrier frequ... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.4 Multiradio Control Services | |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.4.1 Overview on Multiradio Control Services | Table 8.3 describes an overview on Multiradio Control Services which are associated with MRC. Class definition and related operations are described in clause 8.5. Table 8.3: Overview on Multiradio Control Services Multiradio Control Services Explanation Synchronize Radio Time MRC request all the active URAs to operate ... |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.4.2 Messages for Multiradio Control Services | The interfaces for Multiradio Control Services are used to transmit the following messages: • From RCF to URA: - Request of synchronize radio time. • From URA to RCF: - Confirmation of synchronize radio time. - Failure of synchronize radio time. |
0f1830d24a91bc887597422b8f9d5f14 | 103 681-3 | 8.5 Class Definitions for Interface | Each interface class related to gURAI can be defined using the template presented in clause 6.2 and in accordance with the UML diagram of figure 8.1 which specifies the interface classes related to gURAI. Tables 8.1 to 8.3 specify all the operations related to the three interface classes above described. Table 8.4: Rad... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 1 Scope | The scope of the present document is to define the Radio Interface Engine related system architecture. The work is based on the system requirements defined in ETSI TS 103 655-1 [1], and the feasibility study including Use Cases defined in ETSI TR 103 587 [i.1]. |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 2 References | |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-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... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-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... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 3 Definition of terms, symbols and abbreviations | |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 3.1 Terms | Void. |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 3.2 Symbols | Void. ETSI ETSI TS 103 655-2 V1.1.1 (2021-02) 7 |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: GNSS Global Navigation Satellite System LLC Logical Link Control MAC Medium Access Control PER Packet Error Rates PHY Physical Layer QoS Quality of Service RAT Radio Access Technology RIE Radio Interface Engine RIEF Radio Interface Engine Func... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 4.1 Introduction | The present clause introduces three options for the architectural reference model for the Radio Interface Engine. One of the three options shall be selected for implementation: • Option 1: A general basic approach of an architecture reference model is proposed including the Radio Interface Engine Function (RIEF), Infor... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 4.2 Architecture Reference Model (Option 1) | The Radio Interface engine is interacting with Layer-1 (physical layer), and Layer-2 (medium access control layer) as well as logical link control (LLC) layers such as IEEE 802.2 [i.3] LLC or 3GPP Radio Link Control (RLC). Layer 3 and above Network 1 (e.g., 3GPP Rel. 14) Network N (e.g., WiFi) ... LLC_RLC_SAP LLC_RLC_S... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 4.3 Architecture Reference Model (Option 2) | The 2nd option for an architecture reference model complements Option 1 introduced in clause 4.2 by adding an Information Validation Function as illustrated in Figure 3. Layer 3 and above Network 1 (e.g., 3GPP Rel. 14) Network N (e.g., WiFi) ... LLC_RLC_SAP LLC_RLC_SAP Radio Interface Engine Function (RIEF) RIEF_LINK_S... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 4.4 Architecture Reference Model (Option 3) | The 2nd option for an architecture reference model introduces a variant of option 2 defined in clause 4.3. The Information Validation Function is integrated into the RIEF. Layer 3 and above Network 1 (e.g., 3GPP Rel. 14) Network N (e.g., WiFi) ... LLC_RLC_SAP LLC_RLC_SAP Radio Interface Engine Function (RIEF) RIEF_LINK... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 5 Reference Points | The reference points in this clause are for illustration purposes only. This clause does not preclude any specific network deployment architecture. Radio Interface Engine Function (RIEF) Information Function Client Side Radio Interface Engine Function (RIEF) Information Function Network Side RP1 RP2 RP3 RP4 Radio Inter... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 6 Service Access Points | |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 6.1 Introduction | The present clause introduces the service primitives for each of the SAPs. |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 6.2 SAPs required for RIEF_SAP | Table 3 Service Primitives Comments RIEF_SAP_Register Register to the Radio Interface Engine Function. RIEF_SAP _Deregister De-register from the Radio Interface Engine Function. RIEF_SAP_ProvideInformation Provide Information to the the Radio Interface Engine Function, typically valid for a given geographic location an... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 6.3 SAPs required for RIEF_LINK_SAP | Table 4 Service Primitives Comments RIEF_LINK_SAP_Register Register to the Radio Interface Engine Function. RIEF_LINK_SAP _Deregister De-register from the Radio Interface Engine Function. RIEF_LINK_SAP_ProvideInformation Provide Physical Layer and/or Medium Access Control Layer Information to the the Radio Interface En... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 6.4 SAPs required for IN_LINK_SAP | Table 5 Service Primitives Comments IN_LINK_SAP_Register Register to the Information Function. IN_LINK_SAP _Deregister De-register from the Information Function. IN_LINK_SAP_ProvideInformation Provide Information to the Information Function, typically provided by a sensor for a given geographic location and time. IN_LI... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 6.5 SAPs required for INF_VAL_SAP | Table 6 Service Primitives Comments INF_VAL_Register Register to the Information Validation Function INF_VAL_Deregister De-register from the Information Validation Function INF_VAL_RequestValidation Request validation of information INF_VAL_ProvideValidationAssessment Provides result of validation assessment of informa... |
81a00a22c79d05787ec29a56a0c5b60a | 103 655-2 | 7 High level operating procedures | 7.1 Procedures for Network requesting information from Radio Interface Engine Function (Option 1) In the present clause, message exchanges are defined for the 1st option of an architecture reference model as defined in clause 4.2 of the present document: a communication component interacts with the RIEF in order to req... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 1 Scope | The present document defines an information model and protocol for multiradio interface for reconfigurable RE. 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 reconfigurable RE define... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 2 References | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 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... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 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... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 3 Definition of terms, symbols and abbreviations | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: association: logical communication link to a Radio Access Network or a peer equipment NOTE 1: Typically, some control signalling is necessary to maintain the association. No user data transfer may occur with only an association present, but a data flo... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 3.2 Symbols | Void. |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One BLER BLock Error Rate CM Configuration Manager CSL Communication Services Layer FC Flow Controller gMURI generalized Multiradio Interface gRPI generalized Radio Programming Interface gRRFI generalized Reconfi... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 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... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 5 System Identification | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 5.1 Radio Computer Structure | Figure 5.1 illustrates how CSL and RCFs interact with each other using gMURI. ETSI ETSI TS 103 681-1 V1.1.1 (2020-03) 10 Figure 5.1: Interconnection between CSL and RCF using gMURI for Reconfigurable RE As shown in figure 5.1, gMURI supports 3 kinds of services: • Administrative Services - These services are used by so... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 5.2 gMURI System Requirement Mapping | The Radio Computer components above described shall support the gMURI system requirements shown in table 5.1 and described in clauses 6.1 and 6.2 of ETSI TS 103 641 [1]. Table 5.1: Mapping of Radio Computer Components to the system requirements described in ETSI TS 103 641 [1] Entity/Component/Unit System Requirements ... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 6 Notational Tools | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 6.1 Notational Tool for Information Model Classes | In the present document, information model classes are used as defined in annex B.1 of IEEE 1900.4TM-2009 [i.3]. |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 6.2 Notational Tool for Interface Classes | Table 6.1 shows a template for defining interface classes for gMURI. Each interface class for gMURI will be defined in clause 8.5 in accordance with the template shown in table 6.1. Table 6.1: Template for defining Interface Classes Class<Class name>[(abstract class)] <Description of the class> OPERATIONS <Operation na... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 7 Information Model for Radio Computer | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 7.1 General | Figure 7.1 shows the UML class diagram for Radio Equipment which consists of one or multiple Radio Computers. RadioEquipment RoutingEntity 1..* 1 REProfile -REID: NameType 1 1 RECapabilities -listOfSupportedOptions: REOptions -listOfSupportedRadioInterfaces: RadioInterfaces -hardwareProfile: HardwareInfo -softwareProfi... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 7.2 Radio Computer | Figure 7.2 shows the UML class diagram for Radio Computer classes related to gMURI which are required to support software reconfiguration. <<interface>> IgMURI RadioComputer -RCID: NameType RCMeasurements -listOfActiveMeasurements: ActiveMeasurementsList RCConfiguration Link RCCapabilities -listOfSupportedOptions: RCOp... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 7.3 Class Definitions for Information Model | Each class of Radio Computer can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of figure 7.2 which specifies the relations among all the classes of Radio Computer. Radio Computer classes defined in this way are shown in tables 7.1 to 7.17. ETSI ETSI TS 103 681-1 V1.1.1 (20... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8 Interface Definition | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.1 Interface Overview | RadioComputer RCUser |gMURI Figure 8.1: Multiradio Interface (gMURI) Figure 8.1 illustrates the relationship among RadioComputer, RCUser, and gMURI. As shown in figure 8.1, gMURI is the provided interface to Radio Computer, while the gMURI is the required interface to RCUser. Figure 8.2 illustrates a UML diagram for gM... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.2 Administrative Services | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.2.1 Overview on Administrative Services | Table 8.1 describes an overview on Administrative Services which are associated with Administrator. Class definition and related operations are described in clause 8.5. ETSI ETSI TS 103 681-1 V1.1.1 (2020-03) 23 Table 8.1: Overview on Administrative Services Administrative Services Explanation installation/uninstallati... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.2.2 Messages for Administrative Services | The interfaces for Administrative Services are used to transmit the following messages: • From CSL to RCF: - Request of installation/uninstallation of an URA. - Request of creating/deleting an instance of an URA. - Request of updating an instance of an URA. - Request of getting/configuring parameters of an URA. - Reque... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.3 Access Control Services | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.3.1 Overview on Access Control Services | Table 8.2 describes an overview on Access Control Services which are associated with MPM. Class definition and related operations are described in clause 8.5. Table 8.2: Overview on Access Control Services Access Control Services Explanation URA List When the MPM of reconfigurable RE activates URA(s) and/or creates ass... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.3.2 Messages for Access Control Services | The interfaces for Access Control Services are used to transmit the following messages: • From CSL to RCF: - Request of activation/deactivation of an URA. - Request of update of an URA. - Request of installed/instantiated/activated URA(s) list. - Request of start/stop measurements for radio environment. - Request of me... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.4 Data Flow Services | |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.4.1 Overview on Data Flow Services | Table 8.3 describes an overview on Data Flow Services which are associated with networking stack. Class definition and related operations are described in clause 8.5. Table 8.3: Overview on Data Flow Services Data Flow Services Explanation Sending User Data In order to transmit user data through a particular data flow ... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.4.2 Messages for Data Flow Services | Interfaces for Data Flow Services are used to transmit the following messages: • From CSL to RCF: - Request of user data transfer (transmission: SendUserData, reception: ReceiveUserData). ETSI ETSI TS 103 681-1 V1.1.1 (2020-03) 26 • From RCF to CSL: - Confirmation of user data transfer. - Failure of user data transfer.... |
943b8112ccedad49bc8ee8f71a858b75 | 103 681-1 | 8.5 Class Definitions for Interface | Each interface class related to gMURI can be defined using the template presented in clause 6.2 and in accordance with the UML diagram of figure 8.2 which specifies the interface classes related to gMURI. Tables 8.4 to 8.6 specify all the operations related to the three interface classes above described. Table 8.4: IAd... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.