hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.3.4 Required data | For creating an EI job of a certain EI type, the Near-RT RIC provides the EI job identifier and the EI job information, the callback URI for EI job result delivery, and optionally the callback URI for EI job status notifications. EI job information includes the EI job definition that is formulated based on, and validat... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4 Query EI jobs use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4.1 Background and goal of the use cases | The query EI jobs use cases define how Near-RT RIC can query for information on existing EI jobs. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Handles EI job. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 32 b) Responds to queries for EI job identifiers and EI job information. 2) Near-RT RIC: a) Discovers EI jobs available in Non-RT RIC. b) Retrieves EI job information. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4.3.1 Query EI job identifiers | Table 7.4.3.1-1: Query EI job identifiers use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to discover job identifiers for EI jobs that exist in Non-RT RIC Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions EI jobs exist in Non-RT RIC Pre-condi... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4.3.2 Query EI job | Table 7.4.3.2-1: Query EI job use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to retrieve information about an EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI job identifier known to the Near-RT RIC corresponds to an existing ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.4.4 Required data | For querying EI job identifiers, the Near-RT RIC provides optionally an EI type identifier as filter parameter. For querying EI job, the Near-RT RIC provides an EI job identifier. EI job information includes the EI job definition. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.5 Update EI job use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.5.1 Background and goal of the use cases | The update EI job use cases define how Near-RT RIC can update an existing EI job. Near-RT RIC provides updated EI job definition information. The reason for the update can be related to state of the EI type, EI job status and previously received EI job results. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.5.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Handles EI jobs for available EI types. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 34 2) Near-RT RIC: b) Updates EI job in Non-RT RIC that it has created. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.5.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.5.3.1 Update EI job | Table 7.5.3.1-1: Update EI job use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to update an existing EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI job identifier known to the Near-RT RIC corresponds to an existing EI job tha... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.5.4 Required data | For updating an EI job, the Near-RT RIC provides the EI job identifier and updated EI job information and/or callback URI for EI job status notifications. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.6 Delete EI job use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.6.1 Background and goal of the use cases | The delete EI job use cases define how Near-RT RIC can delete an EI job. The reason for the deletion can be related to the state of the EI type, EI job status and previously received EI job results. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 35 7.6.2 Entities/resources involved in the use cases 1) Non-RT RIC: a) Handles EI ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.6.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.6.3.1 Delete EI job | Table 7.6.3.1-1: Delete EI job use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to delete an existing EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI job identifier known to the Near-RT RIC corresponds to an existing EI job tha... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.6.4 Required data | For deleting an EI job, the Near-RT RIC provides the EI job identifier. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7 EI job status use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7.1 Background and goal of the use cases | The EI job status use cases define how Near-RT RIC can detect status, and changes in status, of an EI job. EI job status information is provided by the Non-RT RIC and is used by Near-RT RIC when managing EI jobs. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 36 |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Handles EI job and responds to queries for EI job status. b) Notifies Near-RT RIC about changes in EI job status. 2) Near-RT RIC: a) Requests EI job status. b) Receives notifications about changes in EI job status. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7.3.1 Query EI job status | Table 7.7.3.1-1: Query EI job status use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to retrieve EI job status information for an existing EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI job identifier known to the Near-RT RIC... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7.3.2 Notify EI job status | Table 7.7.3.2-1: Notify EI job status use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to receive EI job status information for an existing EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions Near-RT RIC has the schema for interpretating ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.7.4 Required data | EI job status information includes the EI job status that is formulated based on, and validated against, the EI job status schema. The EI job status information includes indication if EI job is enabled or disabled. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8 EI delivery use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8.1 Background and goal of the use cases | The EI delivery use cases define how Non-RT RIC delivers EI job results to Near-RT RIC based on an EI job. Depending on the EI job definition, the EI job result can be delivered in one delivery message or in repeated delivery messages. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Handles EI job and delivers EI job results. 2) Near-RT RIC: b) Receives EI job result related to an EI job it has created. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 38 |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8.3.1 Deliver EI job result | Table 7.8.3.1-1: Deliver EI job result use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to deliver EI job result based on an EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-P Consumer Assumptions There is enrichment information based on the EI job definition ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8.3.2 Deliver EI job results | Table 7.8.3.2-1: Deliver EI job results use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to deliver EI job results based on an EI job Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-P Consumer Assumptions There is enrichment information based on the EI job definitio... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.8.4 Required data | EI job result information contains the enrichment information requested in the EI job definition. It is formulated based on, and validated against, the EI job result schema. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 40 Annex A (informative): Change history Date Revision Description 2022.07.30 01.00 First version 2022.11.17... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 1 Scope | The present document defines an electronic interface for the exchange of information relating to the establishment and management of Lawful Interception. Typically, this interface would be used between a central LI administration function and the network internal interception points. Typical reference models for LI def... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 2 References | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 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... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 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... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 3 Definition of terms, symbols and abbreviations | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 3.1 Terms | For the purposes of the present document, the following terms apply: attestation: action of a component to respond to an attestation request of a (remote) verifier with a response (also called a quote) that via a digitally signature links the response data to an identity coupled to the component with a predetermined (o... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 3.2 Symbols | Void. ETSI ETSI TS 104 000 V1.3.1 (2025-07) 9 |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 5G Fifth Generation (of mobile network technology) ADMF ADMinistration Function API Application Programming Interface ARP Attestation Relying Party AVS Attest Verifier Service CA Certificate Authority CC Content of Communication CISM Container... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 4 Reference model | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 4.1 Overview | X0 provides a means of establishing trust between an LI Administration Function (ADMF) and an Element of LI (ELI) created in a network and allows configuration of the ELI for other LI interfaces ("Xn"). This involves a sequence of phases, described in table 4.1-1 below. Table 4.1-1: Phases of the X0 reference model # P... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 4.2 Relationship with Xn interfaces (X1, X2 and X3) | Since there can be several Xn interfaces coupled to the ELI, the client certificate associated with the X0 interface is used as the ELI identity, and the client certificates for X1, X2, X3, etc. are logically linked to the X0 client certificate by requiring that the certificate signing requests go over the mTLS connect... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5 Procedures | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.1 Phases | When the network function is instantiated, the X0 interface shall be configured. To achieve this, the instantiation process shall use mechanisms beyond the X0 interface itself. On the other hand, to have as much as possible of the configuration of X0 to use the X0 interface itself, the instantiation is performed in pha... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.2 Pre-configuration (Phase 0) | Prior to the creation of an X0 interface between the ADMF and the X0 interface instance in an ELI, several configurations shall take place at both ends of the X0 connection. Since this configuration takes place before the NF with the associated ELI function is instantiated, these configurations are referred to as X0 pr... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.3 NF Discovery (Phase 1) | When the NF is instantiated through orchestration via MANO/CISM the ADMF will receive notifications containing information of the new instance. It is assumed that in phase 0 ADMF has subscribed to MANO/CSIM to receive such notifications and the LIPF in the ADMF will handle the notifications, see ETSI TS 104 007 [2]. NO... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.4 Attestation (Phase 2) | The X0 interface instance and ELI will conduct attestation operations. As a result, the AVS will provide the ARP in LISE with: • The result of attestation (successful or failure, and time of attestation). • A randomly created identifier associated with the attested interface instance and NFIID. • A public-key referred ... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.5 Trust Bootstrap finalization (Phase 3) | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.5.1 Procedure | Having performed the discovery and the attestation having been conducted, the LIPF can check if the attest and the identifiers of the NF line-up, thus indicating that a trusted X0 instance is present in the NF where the X0 has an X0PUB. The X0PUB is a public portion of a public-private key pair supporting authenticatio... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.5.2 Trust bootstrap without attestation | This clause describes which provisions need to be made to make X0 trust bootstrap work without attestation. The result of the attestation is that the LISE later can consult the AVS to check the identifiers and the X0PUB key. The LISE can perform its task for the X0 trust bootstrap if it is configured with these paramet... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.6 Registration and certificate provisioning (Phase 4) | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.6.1 Procedure | After the NF is up and running, the X0 in ELI starts the interactions to obtain a certificate for X0 from the LICA on the basis that the ADMF has attested the ELI X0 interface instance. The interactions are grouped into the following steps: • First the ELI creates a self-signed X509 certificate using the key pair whose... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.6.2 Certificate provisioning with CMP | In case of CMP, the ELI creates a public-private key pair for X0, and uses the IAK/password and the provided CSR parameters to create a certificate request message, e.g. for use in CMP. Then, the ELI uses the certificate management protocol to send the certificate request message to the LICA. The LICA uses the IAK/pass... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.7 X0 and Xn Configuration (Phase 5) | After ELI has obtained the X0 end-entity certificate from the LICA, it shall henceforth use this certificate for its X0 HTTPS connection to LISE for further configuration of X0 and the other X interfaces. NOTE: It is assumed that the client certificate used for the HTTPS connection is used in the LICREPF to enforce acc... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.8 Provisioning of certificates for X1, X2 and X3 (Phase 6) | While the certificate enrolment of the X interfaces is basically identical to the one for X0, the preparations differ (the present clause details the steps). In the present clause Xn stands for any of the X1, X2 or X3 interfaces. When the X0 interface is configured, through the configuration in clause 5.7 the ELI knows... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.9 Image key insertion and decryption (Phase 7) | The ADMF can use the X0 interface to send to the ELI an IMK key which can be used for decryption of software images or configuration data, see clause 5.1. The IMK is sent in a key container. The ADMF can use the X0 interface to instruct the ELI about what to do with the key as part of the ImageKeyDetails, see clause 6.... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 5.10 Retrieval and check of ELI configuration | After the ELI successfully gets the configuration data and sets up the supported Xn interfaces, the LISE can retrieve the configuration data in use on the ELI for integrity checks. To do this, the LISE shall do the following: • Send a GetAllConfigurationRequest message (see clause 6.2.7.1), which requests the ELI to pr... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6 X0 protocol | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.1 Basic Concepts | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.1.1 Reference model for X0: requesting and responding | X0 transactions consist of a request followed by a response. Requests may be sent in either direction i.e. with either the ELI or the LISE initiating the request. Figure 6.1.1-1 shows a response-request model, with the ELI initiating the request and the LISE responding with the requested data. Figure 6.1.1-1: Generic r... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.1.2 The lifecycle of an ELI configuration | An ELI configuration is uniquely associated with the X0 interface established between the ELI and the LISE of the ADMF. Each ELI configuration is uniquely identified by an ELI Identifier (ELIID) assigned by the LISE as part of the Registration phase (see clauses 5.6 and 6.2.3). When the LISE detects that an ELI has bee... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.1.3 The lifecycle of an X0 request/response | Each request and response shall be identified by an X0TransactionID. The requester (LISE or ELI) shall assign an X0TransactionID as a version 4 UUID as per IETF RFC 4122 [12]. The response shall be sent without delay and shall be sent within TIME1X0 of receiving the request. TIME1X0 shall be configurable and by default... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2 Message Definitions | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.1 X0 Message | X0 messages contain information as defined in table 6.2.1-1. The information is Mandatory, Optional or Conditional as shown in the last column. ETSI ETSI TS 104 000 V1.3.1 (2025-07) 28 Table 6.2.1-1: X0 Message Field Description Format M/C/O admfIdentifier Identifies the ADMF uniquely to the ELI. Required to match the ... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.2 Error responses | If the Responder is unable to parse an X0 Request, or cannot fulfil the X0 Request, then it shall respond with an ErrorResponse. If the Responder is unable to determine the correct ADMF or ELIID values (e.g. because the original Request cannot be parsed), it shall use the values provided in the client certificate (see ... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.3 Registration message definitions | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.3.1 RegistrationRequest | The RegistrationRequest message is sent by ELI to the LISE to perform initial registration and obtain the necessary information to perform X0 certificate enrolment (see clause 5.6). In addition to the details in clause 6.2.1, it shall contain the following information. Table 6.2.3.1-1: RegistrationRequest Field Descrip... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.3.2 RegistrationResponse | The RegistrationResponse message is sent by the LISE to the ELI as a response to a RegistrationRequest to signal that registration has been successfully completed (see clause 5.6.1) and that the ELI shall now proceed with certificate enrolment (see clauses 5.6.2 and 5.8). If the registration procedure is not successful... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.4 Xn certificate enrolment message definitions | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.4.1 XnCertificateEnrolmentRequest | The XnCertificateEnrolmentRequest message shall be sent by the ELI to the LISE after the ELI has successfully retrieved its configuration information for the first time (see figure 5.7-1 in clause 5.7). If the ELI has not yet retrieved its initial configuration for the first time, the LISE shall respond to the XnCertif... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.4.2 XnCertificateEnrolmentResponse | The XnCertificateEnrolmentResponse message shall be sent by the LISE to the ELI as a response to a XnCertificateEnrolmentRequest if the LISE is able to enter the ELI into enrolment for all of the interfaces requested (see table 6.2.4.2-1). If enrolment fails for any of the requested interfaces, then the LISE shall term... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.5 Configuration message definitions | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.5.1 ConfigurationRequest | The ELI may send a ConfigurationRequest to the LISE at any time after X0 enrolment to request configuration information for the ELI's Xn interfaces. The ELI shall send a ConfigurationRequest to the LISE immediately after successful X0 certificate enrolment (see clause 5.7). This request shall provide a notification URL... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.5.2 ConfigurationResponse | The ConfigurationResponse message is sent by the LISE to the ELI as a response to a successful ConfigurationRequest message. In addition to the details in clause 6.2.1, it shall contain the following information. Table 6.2.5.2-1: ConfigurationResponse Field Description Format M/C/O listOfConfigurationDetails List of co... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.6 Notification message definitions | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.6.1 NotificationRequest | Whenever the configuration of the ELI is required to change because the ADMFs has changed the ELI configuration in the repository the LISE shall send a NotificationRequest message to the ELI The ELI shall respond with a NotificationResponse message (see clause 6.2.6.2) and then issue ConfigurationRequest message (see c... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.6.2 NotificationResponse | The ELI shall respond to a NotificationRequest message from the LISE with a NotificationResponse message. The NotificationResponse has no additional parameters beyond those given in clause 6.2.1. |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.7 Get message definitions | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.7.1 GetAllConfigurationRequest | Whenever the LISE needs to retrieve the configuration parameters in the ELI, the LISE shall send a GetAllConfigurationRequest message to the ELI. The ELI shall respond with the GetAllConfigurationResponse message. The GetAllConfigurationRequest message has no additional parameters beyond those given in clause 6.2.1. |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 6.2.7.2 GetAllConfigurationResponse | The ELI shall respond to a GetAllConfigurationRequest message from the LISE with a GetAllConfigurationResponse message including the configuration data for each supported Xn interface and the certificate enrolment parameters for each certificate profile. If the ELI is not able to respond to the GetAllConfigurationReque... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 7 Transport and encoding | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 7.1 Overview | The present document defines a single profile for transport and encoding of X0 messages ("profile A"). |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 7.2 Profile A | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 7.2.1 Encoding | Samples, which provide an informative example for implementations of the present document, are available together with the normative XSD at https://forge.etsi.org/rep/li/schemas-definitions/- /tree/spec/104000/1.3.1/104000?ref_type=tags which accompanies the present document. In the event of a discrepancy between the X... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 7.2.2 Transport | HTTPS shall be used as per IETF RFC 9110 [5]. The details relating to HTTP are given in this clause and the details relating to TLS are specified in clause 8.2. ETSI ETSI TS 104 000 V1.3.1 (2025-07) 35 In this clause, the term HTTP is used (it is implicit that it is in fact HTTPS, i.e. that the HTTP is used over TLS). ... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 7.2.3 HTTP configuration | HTTP version 1.1 or HTTP/2 shall be used. LISE and ELI implementations shall support both. Where used, HTTP version 1.1 shall be used as per IETF RFC 9110 [5], IETF RFC 9112 [6] and related specifications. NOTE: HTTP/1.1 defaults to the use of "persistent connections" (see IETF RFC 9112 [6], section 9.3). Implementers ... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8 Certificate profiles for X0 | |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8.1 Overview | The X0 interface uses certificates from the LICA for the X0 channel that is utilized for the configuration of X1, X2 and X3. In addition, the X0 interface uses a self-signed client certificate during the ELI registration (see clause 5.6). The public key of this certificate is the same as the X0PUB key that the attested... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8.2 URN format | A certificate binding URN has the following format, with the placeholders {role} and {identifier} given as per table 8.2-1. Urn:etsi:li:x0-binding:{role}:{identifier} Table 8.2-1: Certificate binding URN format Field Description Format Role String indicating the role of the party presenting the certificate. One of "ADM... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8.3 Certificate Binding Validity | A certificate binding URN presented in a client or server certificate as part of the transmission of an X0 message shall be considered valid if and only if all the following conditions are met: • It follows the format given in table 8.2-1. • The Role value correctly matches the expected role of the presenting party (i.... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8.4 ELI client certificate for registration | The procedure in clause 5.6 where the ELI registers at LISE in ADMF shall use a self-signed certificate with a profile complying to the requirements in clause 8.1 and details of table 8.4-1. Table 8.4-1: Client certificate profile for ELI registration Field Description Value Basic Constraints Certificate shall function... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8.5 X0 client and server certificates | Certificates issued by the LICA and used on the X0 channel shall, in addition to profile requirement in clause 8.1, be profiled as indicated in table 8.5-1. Table 8.5-1: Client and Server end-entity certificate profile for X0 channel Field (attribute) Description Value Subject commonName Use is not recommended. If pres... |
69c98c511bab602e2d88e5a50cb97bb3 | 104 000 | 8.6 Authentication and binding verification | Implementations shall perform mutual authentication using X.509 certificates following IETF RFC 6125 [11] with the additional provisions for X0 as detailed in clauses 8.1 through 8.4. Implementations shall ensure that it is possible to configure which certificates are used. Implementations shall also perform a verifica... |
d8aebb5c51bcbe988788dc4270a394e1 | 104 040 | 1 Scope | The present document describes the O-RAN specified RAN Function-specific Service Models supported over E2 (E2SM) and specifies the common elements for use in E2 service models. |
d8aebb5c51bcbe988788dc4270a394e1 | 104 040 | 2 References | |
d8aebb5c51bcbe988788dc4270a394e1 | 104 040 | 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... |
d8aebb5c51bcbe988788dc4270a394e1 | 104 040 | 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 1: While any hyperlinks... |
d8aebb5c51bcbe988788dc4270a394e1 | 104 040 | 3 Definition of terms, symbols and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.