hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 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... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 3 Definition of terms, symbols and abbreviations | |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [i.1] and ISO/IEC 9646-7 [i.2] apply. |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 3.2 Symbols | Void. ETSI ETSI TS 103 825 V1.1.1 (2022-09) 6 |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AML Advanced Mobile Location ATS Abstract Test Suite BV Valid Behaviour HTTP HyperText Transfer Protocol HTTPS HTTP Secure ID Identity IDE Integrated Development Environment IFS Interoperable Functions Statement IMEI International Mobile Equip... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 4 Prerequisites and Test Configurations | |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 4.1 Test Configurations | Test configurations capture and describe the components identified in the tests and the connections between them. For the present test suite, two (2) configurations are identified and listed in the present clause. For each test configuration two (2) main components are identified: the IUT implementing the AML specifica... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 4.2 Protocol Implementation Conformance Statement (PICS) | The "Protocol Implementation Conformance Statement" (PICS) identifies the standardized functions of an IUT. These functions can be mandatory, optional or conditional (depending on other functions), and depend on the role played by the IUT. The PICS can also be used as a proforma by a vendor to identify the functions th... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 5 Test Suite Structure (TSS) | |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 5.1 Overview | The test suite structure identifies grouping of test purposes and serves a base for grouping of Test Case in the ATS (Abstract Test Suite). The Test Suite structure is used for the creation of identifiers of Test Purposes. Table 5.1-1 identifies the Test Suite Structure for the AML Conformance test suites. Documentatio... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 5.2 Test groups specifications | The groups identify the different transport mechanisms of the AML data. Moreover, test purposes are identified and categorized by a sequential two-digits number (uniquely assigned upon definition of each test purpose) and by the type of test performed. The type of test helps quickly identify the type of behaviour that ... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 5.3 Conventions | The test purposes are primarily developed in textual syntax of TDL-TO, where the Initial Conditions and Expected Behaviour of each Test Purpose is written and shall be interpreted using the TDL-TO notation as defined in ETSI ES 203 119-4 (V1.4.1) [2]. The sources for the Test Purposes are available in https://forge.ets... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 6 AML Test Purposes | |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 6.1 SMS Transmission | TP Id TP_AML_SMS_BV_01 Test Objective Verify that the IUT automatically sends AML via SMS when an emergency call is initiated Reference ETSI TS 103 625 (V1.2.1) [1], clause 5.2, paragraph 2 PICS Selection PICS_SMS_SUPPORT Initial Conditions with { the IUT is configured to the SMS_ENDPOINT entity } Expected Behaviour en... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 6.2 HTTPS Transmission | TP Id TP_AML_HTTPS_BV_01 Test Objective Verify that the IUT automatically sends AML via HTTPS when an emergency call is initiated Reference ETSI TS 103 625 (V1.2.1) [1], clause 5.2, paragraph 2 PICS Selection PICS_HTTPS_SUPPORT Initial Conditions with { the IUT is configured to the HTTPS_ENDPOINT entity } Expected Beha... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 1 Scope | The present document describes the I3C interface for the communication of an SSP, as defined in ETSI TS 103 666-1 [1] using the SCL protocol. The present document details the implementation of MIPI I3C Basic specification [4] for an SSP. Specifically, I3C electrical characteristics, Target state diagram, data link laye... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 2 References | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 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. • In the case of a reference... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 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. • In the case of a reference... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 3 Definition of terms, symbols and abbreviations | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 102 216 [i.1] and the following apply: data transfer: information exchange during an I3C Basic Access between the Controller and the Target NOTE: As defined in I3C Basic [4]. flow control: mechanism of the Data Link Layer that consists of methods appl... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 3.2 Symbols | Void. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Alternating Current ACT ACTivation protocol CCC Common Command Code CLF ContactLess Frontend CLT ContactLess Tunnelling CMD CoMmanD CRC Cyclic Redundancy Check HDR High Data Rate High-Z High Impedance I3C Improved Inter Integrated Circuit I... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 4 Introduction | The Improved Inter Integrated Circuit (I3C) is a serial synchronous half-duplex communication interface between a one or more Controllers and one or more Targets present on the same I3C bus. This clause defines the physical, MAC and data link layers for the I3C interface. Since the terms Master and Salve have been depr... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 5 SCL Under-Layers Protocol Stack | Figure 5-1 illustrates the protocol stack below the SCL supporting the I3C interface. NOTE: The meaning of "SCL" in this clause is the SSP Common Layer as defined in ETSI TS 103 666-1 [1]. Figure 5-1: Protocol stack for I3C Interface SCL MAC Other Physical Layer FRAME TRANSPORT Link Layer (RELIABILITY and DATA FLOW CON... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6 Electrical interfaces | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6.1 Introduction | In the following clauses, an implementation of I3C interface is defined. This implementation, based on MIPI I3C Basic specification [4], allows bi-directional communication and the possibility for the Target device to initiate communication with the Controller when it has data available thus avoiding the necessity for ... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6.2 Physical interface | Figure 6.2-1 illustrates the I3C interface using 2 signals. Figure 6.2-1: I3C electrical interface The I3C interface with 2 signals describes two signals: • SDA: Serial Data line. • SCL: Serial Clock line. The IBI request may be used by the I3C Target as per MIPI I3C Basic specification [4] in cases where the Target ha... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6.3 Electrical characteristics | The provisions of MIPI I3C Basic specification [4], clause 6.1 and clause 6.2 shall apply. Electrical I/O stage characteristics defined in table 82 of MIPI I3C Basic specification [4] shall apply. Support of multiple voltage classes may affect timing parameters specified in clause 6.2 of MIPI I3C Basic specification [4... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6.4 Target state | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6.4.1 Target state definitions | The Target device shall be in one of the following states: • Powered Not Initialized State: - The Target device enters this state as soon as it is powered on and VDD is valid or after a reset. In this state, the Target is not initialized and the I3C module is not ready to send or receive any data. The Controller shall ... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 6.4.2 Target state diagram | Figure 6.4.2-1 shows the diagram of the Target states. ETSI ETSI TS 103 818 V17.1.0 (2023-08) 12 Release 17 NOTE: For the sake of readability, the transitions to the Powered not Initialized state if a reset occurs are not shown. Figure 6.4.2-1: Diagram of the Target states |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7 Data Link Layer | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.1 Overview | Clause 9.1 in ETSI TS 102 613 [2] shall apply. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2 MAC Layer | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.1 Overview | The MAC phase is the initial handshake phase between the I3C Controller and the I3C Target followed by the I3C data transfer phase. Powered not Initalized (VDD ON) Initial (DA not assigned) Idle Active Active Selected Busy Power Saving mode Pro-active (IBI) Exit from CCC or Repeated Start Supported CCC command Or Dynam... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.2 Timing | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.2.1 Timing definitions | Table 7.2.2.1-1 describes the timing parameters of the MAC layer. In addition to these MAC timings, the timing requirements listed in AC electrical characteristics shall apply for all MAC diagrams in the following clauses. Table 7.2.2.1-1: MAC timing parameters Symbol Definition Value (min)/ Reference Description T3 Ta... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.2.2 T3 = Target Resume Time from Power Saving Mode | T3 is the Target Resume Time from the Power Saving Mode. It is Target implementation dependant. The Target reports at initialization in MCT_READY the minimum value of T3 required for the Target to become ready for the I3C Basic Access. Whenever the Controller needs to resume the Target from Power Saving Mode it should ... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3 MAC layer | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3.1 Introduction | As a Target I3C module is normally always ready for an access from the Controller, the Target remains in Idle state. The Controller initiates a MAC phase by issuing an I3C Private Write. The Target will move into (Active-Selected) state when the address sent by the Controller in the address header (MIPI I3C Basic speci... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3.2 Initiation of the data transfer from the Controller | The Controller initiates communication as described in MIPI I3C Basic specification [4], clauses 5.1.2.2 and A.2. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3.3 Initiation of the data transfer from the Target | I3C data transfers are always performed by the Controller. The Target can request a transfer to the Controller through an In Band Interrupt (IBI). Upon reception of the IBI the Controller starts the data transfer as described in clause 5.1.6.2.2 of MIPI I3C Basic specification [4]. IBI is described in MIPI I3C Basic sp... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3.4 Simultaneous initiation of the data transfer from both Controller and Target | The data transfer could be initiated simultaneously by the Controller and the Target module or multiple Target modules and in this case the arbitration will determine which device wins and then continues to send data, as described in MIPI I3C Basic specification [4], clauses 5.1.6 and 5.1.2.2.1. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3.5 MAC activation | The MAC activation procedure shall be the following: • The Controller shall drive the VDD power line ON. • I3C Dynamic Address assignment shall follow the VDD power line on to complete the MAC activation. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.2.3.6 MAC deactivation | The MAC deactivation procedure shall be the following: • The Controller shall put the bus in Idle state. In the present document, MAC deactivation implies the Controller driving the VDD power line off. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.3 Link Layer Frame | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.3.1 Overview | The Controller and the Target exchange Frames. The format of the Frames generated by the Controller and the Target is determined by the link layer and it is shown in figure 7.3.1-1. LPDU Length 16 bit Target address 8 bit LPDU bytes CRC16 16 bit LPDU Link Layer Trailer Link Layer Header Link Layer Frame Length = (LPDU ... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.3.2 Frames generation and transfer rules | The Controller initiates an I3C Basic Access either to send a Frame, or retrieve a Frame from the Target after a MAC access request. If the Controller has a Frame to send or receive, the Controller shall send/receive that Frame in a single I3C Basic Access. Maximum Read and Write lengths are determined by MTU as explai... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.3.3 Data transfer cases | Some of the most representative data transfer cases, based on the Frames generation and transfer rules in clause 7.3.2, are described below. Any Frame sent by the Controller or the Target shall be preceded by a MAC phase issued respectively by the Controller or the Target. Case 1: the Controller initiates the MAC phase... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.4 LLC layers | Three Logical Link Control (LLC) layers are defined in the present document: • SHDLC: this is the generic LLC. SHDLC is defined in ETSI TS 102 613 [2], clause 10. Support of this LLC is mandatory for the Controller and the Target. • CLT: this LLC is used for some proprietary protocol handling. CLT mode is defined in ET... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.5 Interworking of the LLC layers | After the MAC activation, the SHDLC link shall not be established and no CLT session shall be open. Only the MCT LLC shall be used by the Controller and by the Target for the I3C Link Layer initialization. ETSI ETSI TS 103 818 V17.1.0 (2023-08) 20 Release 17 The Controller shall take the following action after a succes... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.6 MCT LLC definition | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.6.1 MCT LPDU structure | The MCT LPDU shall be structured according to figure 7.6.1-1. Figure 7.6.1-1: MCT LPDU structure The meaning of MCT_CTRL and MCT_DATA is given in table 7.6.1-1. Table 7.6.1-1: Meaning of MCT_CTRL and MCT_DATA MCT_CTRL Meaning MCT_DATA 00000 MCT_READY Sent from the Target to the Controller See table 7.6.3-1 00010 MCT_CO... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.6.2 MCT_DATA from Controller | Tables 7.6.2-1, 7.6.2-2 and 7.6.2-3 define the capabilities of the Controller. Table 7.6.2-1: Controller-specific MCT_DATA field Byte Info/parameter Meaning 0 ETSI I3C specification version Specification version to which the Controller is compliant. Defined in table 7.6.2-2 1 Capabilities Defined in table 7.6.2-3. 2, 3... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.6.3 MCT_DATA from Target | Tables 7.6.3-1 and 7.6.3-2 define the capabilities of the Target. ETSI ETSI TS 103 818 V17.1.0 (2023-08) 22 Release 17 Table 7.6.3-1: Target-specific MCT_DATA field (bytes 0…9) Byte Info/parameter Meaning 0 ETSI I3C specification version Specification version to which the Target is compliant. Defined in table 7.6.2-2. ... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.6.4 MCT activation procedure | Target start up time following power on includes the Dynamic Address state. T5 is defined as a minimum delay for the Target to be able to receive a Dynamic Address. The Controller can assign a Dynamic Address at any time after the T5 reported and the initial value of T5 is 1s for the first power on. The T5 shall always... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.7 SHDLC LLC definition | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.7.1 SHDLC overview | The provisions of ETSI TS 102 613 [2], clause 10.1 shall apply. The SWP SHDLC layer is replaced by the I3C SHDLC layer defined in the present document. The SHDLC layer shall ensure that data passed up to the next layer has been received exactly as transmitted i.e. error free, without loss and in the correct order. Also... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.7.2 Endpoints | SHDLC communication occurs between two endpoints. Those endpoints may be either the Controller endpoint or the Target endpoint. There is no priority of traffic. Figure 7.7.2-1: Endpoints In ETSI TS 102 613 [2], clause 10, the term CLF refers to the Controller endpoint and the term UICC to the Target endpoint. |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.7.3 Flow control | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.7.3.1 Overview | Flow control is performed by a transmitter in order to avoid corruption or loss of data. It consists of methods applied by the transmitter and receiver in order to send a maximum number of SHDLC frames that can be accepted by the receiver, after which it shall stop sending data until the receiver sends at least an ackn... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.7.3.2 Flow control based on SHDLC | The method defined in this clause is based on SHDLC flow control, as defined in ETSI TS 102 613 [2]. In addition to the provisions of clause 7.3.2, the total number of bytes transferred on I3C Basic shall be done in a single frame where the maximum frame lengths shall be less than MTU or a window size slot depth. The m... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8 Power management | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.1 Power saving mode | In order to optimize the power consumption, both the Controller and the Target may enter into Power Saving Mode. This clause defines the conditions for the Target to enter into Power Saving Mode and the procedures for the Controller for resuming the Target from Power Saving Mode. The Controller and the Target shall bot... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.2 Conditions for entering Power Saving Mode | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.2.1 Target entering Power Saving Mode | The Target shall not enter into Power Saving Mode, if the Target has issued a MAC access request and is waiting for data transfer from the Controller. The Target may enter into Power Saving Mode in one of the cases below, assuming there is no pending activity: 1) All frames have been transmitted by the Target, acknowle... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.2.2 Controller entering Power Saving Mode | The Controller may enter into an implementation-specific Power Saving Mode at any time, without informing the Target. The Target power source status and capabilities indicated by the Controller at interface initialization shall not change when the Controller enters into Power Saving Mode, is in Power Saving Mode, is re... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.3 Resuming from Power Saving Mode | |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.3.1 Resuming the Target from Power Saving Mode | The Controller may perform one of the following procedures to resume the Target: • Use an out of band line to signal wake up. • Use a private communication using the Target Dynamic Address: - This communication shall be sent without the broadcast address: Sending a private communication without the broadcast address ... |
fcd18c25ac0f919d4bd7711779003696 | 103 818 | 7.8.3.2 Resuming the Controller from Power Saving Mode | If the Controller has entered into Power Saving Mode without sending DISEC CCC to disable the IBI , then it shall resume when the Target initiates a MAC access request. The Target initiates the MAC access request with the procedures as described in clause 7, regardless the power management status of the Controller. Fol... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 1 Scope | The present document is intended to specify the method and computer interface used for secure communication between two users of products based on Multimedia Internet Keying Sakai-Kasahara Key Encryption (MIKEY-SAKKE). It is intended for ensuring a Key Management Server (KMS) is able to securely query other KMSs, with ... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 2 References | |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 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... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 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... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 3 Definition of terms, symbols and abbreviations | |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 3.1 Terms | Void. |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 3.2 Symbols | Void. |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project GAA Generic Authentication Architecture GBA Generic Bootstrapping Architecture HMAC Hash-based Message Authentication Code HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure KDF Ke... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 4 Overview | Any given user of a Vendor Product is managed by one or more KMSs. As defined in IETF RFC 6509 [3] such a KMS acts as a root of trust and distributor of key material, providing the user with its unique private keys, and all the information it requires to ensure it is able to encrypt data for other users managed by this... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 5 Inter-domain communication | |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 5.1 HTTP Interface | A Vendor Product KMS shall provide an HTTP endpoint which shall be secured via TLS 1.2 as defined by IETF RFC 5246 [5] The endpoint may implement TLS 1.3 as defined in IETF RFC 8446 [6]. The KMS may also support TLS Pre-Shared Keys (TLS-PSK) in accordance to IETF RFC 4279 [7]. The TLS Certificate shall be signed. It ma... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 5.2 XML Protection Key | A Vendor Product KMS shall generate a 128-bit key, the XPK. The KMS shall generate a separate XPK for each of the KMSs it desires to establish a secure communication channel with (each KMS if "federates" with). The XPK shall be generated by the Vendor Product KMS using a cryptographically secure random number generator... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 5.3 Setup | To enable secure communication between Vendor Products, each Vendor Product KMS shall provide the following set of data ("credentials") to any external KMS with which it wishes to federate: • KMS Certificate [2] • TLS certificate for the KMS Server and TLS-PSK keys if desired • KMS lookup domain, port and address of th... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6 Discovery procedure | |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.1 Discovery call flow | In order for an initiating client to obtain the required data to establish a communication session, the initiating client's KMS may need to query one or more trusted KMSs with which it has already setup a secure communication channel. For example, the initiating client user "Alice" managed by KMS_A wishes to initiate a... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.2 XML Request | |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.2.1 XML Request format | The requesting KMS shall send an HTTPS POST request to the endpoint with a SHA-256 HMAC signed requesting XML document, and include the following HTTP headers: Content-type: text/xml |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.2.2 Fields | Table 1: KMS Request Certificate Subfields Name Description Version (Attribute) The version number of the certificate type (1.0.0) UserUri The URI of the requesting KMS KmsUri The URI of the responding KMS Time The time of the request in ISO 8601 format [11] ClientReqURL The URL that was queried CanonicalizationMethod ... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.2.3 XML Schema | <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="UserUri" type="xs:string"/> <xs:element name="KmsUri" type="xs:string"/> <xs:element name="Time" type="xs:dateTime"/> <xs:element name="ClientReqUrl" type="xs:string"/> Alice (+123... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.3 XML Response | |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.3.1 XML Response format | The responding KMS shall ensure the requesting address matches the KMS endpoint domain provided during the credentials exchange which occurred prior to responding to the POST request. The responding KMS may send a response or it may block incoming connections from other originating address at the network layer (for exa... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.3.2 Fields | The KMS request shall be named a "SignedKmsResponse" within the XML. This type shall have the following subfields as shown in table 2. ETSI ETSI TS 103 816-5 V1.1.1 (2021-07) 13 Table 2: KMS Response Certificate Subfields Name Description Version (Attribute) The version number of the certificate type (1.0.0) UserUri Th... |
90bab6aa80890ee08ed58db81a3c421b | 103 816-5 | 6.3.3 XML Schema | <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="UserUri" type="xs:string"/> <xs:element name="KmsUri" type="xs:string"/> <xs:element name="KmsLookupResult"> <xs:complexType> <xs:sequence> <xs:element ref="UserUri"/> <xs:element ... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 1 Scope | The present document is intended to specify the group conferencing interface used for encrypted voice communications. It is intended for use in connecting products based on Multimedia Internet Keying Sakai-Kasahara Key Encryption (MIKEY-SAKKE) domains and to validate products. |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 2 References | |
8e56323162efa63c2224e9cee1fcf689 | 103 816-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... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-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... |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 3 Definition of terms, symbols and abbreviations | |
8e56323162efa63c2224e9cee1fcf689 | 103 816-4 | 3.1 Terms | Void. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.