hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4 General description | The present document specifies the physical layer for the Asynchronous Access option of the Return Link using the Spread Spectrum Aloha (SSA) technique [i.1] and [i.2]. The present document has similarities with 3GPP specifications [i.9], [i.10] and the differences are described. The present document covers the Return-... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.1 Relationship to other layers | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.1.1 General Protocol Architecture | The overall protocol architecture for the return link of S-MIM asynchronous access is shown in Figure 4.1. USER PLANE MANAGEMENT PLANE CONTROL PLANE Modulation & Transmission Header Compression Encryption (LL) Encapsulation & Addressing Transmission Mode PHY Link Layer EC NEC RLE NCC ACK Mode U-ACK Mode UsCC PCCH PDCH ... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.1.2 Services provided to higher layers | The physical layer offers data transport services to higher layers. The physical layer is expected to perform the following functions in order to provide the data transport service: - Error detection on transport channel and indication to higher layers. - FEC encoding/decoding of transport channels. - Rate matching of ... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.2 Transmitter functional architecture | In the transmission direction Physical Layer functional block diagram is shown in Figure 4.2. Figure 4.2: Transmitter Functional Block Diagram |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.3 Channel descriptions | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.3.1 Transport channel | There is a single transport channel: the Random Access Channel (RACH). The RACH is characterized by limited size data burst length, a collision risk and by the use of open loop power control. Three possible nominal sizes of the RACH data burst length are supported, namely 300, 600 and 1 200 bits. Depending on the effec... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 4.3.2 Physical channels | Two physical channels are defined, namely the PDCH (Physical Data Channel) used to carry the RACH data burst and the PCCH (Physical Control Channel) used to carry physical layer signalling information. The PDCH and the PCCH are I/Q code multiplexed to form an Up-Link Burst (ULB), composed of three parts (Figure 4.3): •... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5 Physical Channel Structure | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5.1 PDCH structure | As shown in Figure 5.1, the PDCH data burst (after channel encoding according to clause 6.1), is divided into a variable number of frames ranging from 3 (Option 1) up to 24 (Option 4). Each frame has a fixed duration of 10 ms. The PDCH length (in time or, equivalently, in frames) is indicated with the term TTI (Transmi... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5.1.1 CRC format | The PDCH includes an optional 16 bit or 8 bit CRC. If a CRC is used the parity bits are generated by one of the following cyclic generator polynomials: gCRC16(D) = D16 + D12 + D5 + 1 gCRC8(D) = D8 + D7 + D4 + D3 + D + 1 ETSI ETSI TS 102 721-3 V1.2.1 (2013-08) 13 Denote the bits in a RACH data burst delivered to layer 1... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5.2 PCCH structure | The PCCH consists of Np known pilot bits to support channel estimation for coherent detection and NF bits for the TFI (Transport Format Indication) message per slot. The size of each PCCH slot is always 10 bits, as shown in Table 5.2. The TFI carries information associated with the packet format and packet length. The ... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5.2.1 Pilot symbols format | Pilot symbols transmitted on the PCCH are obtained through a ML PN generator. The scrambling sequence is a segment of an ML sequence defined by polynomial 1+X4+X9. The initial loading of the shift register shall be equal to 101000000 as indicated in Figure 5.3. The shift register shall be reset at the initial loading a... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5.2.2 Transport Format Indication format | The TFI message carries 5 information bits which are thus able to address up to 32 different PDCH configurations. This message is encoded in a (15, 5) codeword obtained extending an ML code (15, 4) generated by the primitive polynomial h(x)=x4+x+1 with the antipodal codewords. NOTE: The generator polynomial is thus g(x... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 5.3 Transport-to-Physical Channel Mapping | The mapping between the transport channel defined in clause 4.3.1 and the physical channels defined in clause 4.3.2 is unambiguously determined through Table 5.1 depending on the chip rate, the spreading factor and the required PDCH data burst length (or equivalently, the required info bits per burst). These parameters... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6 Channel Coding and Interleaving | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.1 Channel Coding | The Turbo-coder has a nominal code rate of 1/3, but may slightly differ from 1/3 owing to the rate matching capability as defined in clause 6.2.2. The following turbo-code specifications are taken from the 3GPP [i.9] specifications. The scheme of Turbo coder is a Parallel Concatenated Convolutional Code (PCCC) with two... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.1.1 Constituent code | The transfer function of the 8-state constituent code for PCCC is: G(D) = ⎥ ⎦ ⎤ ⎢⎣ ⎡ ) ( ) ( ,1 0 1 D g D g , where g0(D) = 1 + D2 + D3, g1(D) = 1 + D + D3. The initial value of the shift registers of the 8-state constituent encoders shall be all zeros when starting to encode the input bits. Output from the Turbo coder... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.1.2 Trellis termination for turbo coder | Trellis termination is performed by taking the tail bits from the shift register feedback after all information bits are encoded. Tail bits are padded after the encoding of information bits. The first three tail bits shall be used to terminate the first constituent encoder (upper switch of Figure 6.1 in lower position)... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.1.3 Turbo code internal interleaver | The Turbo code internal interleaver consists of bits-input to a rectangular matrix, intra-row and inter-row permutations of the rectangular matrix, and bits-output from the rectangular matrix with pruning. The bits input to the Turbo code internal interleaver are denoted by K x x x x , , , , 3 2 1 K , where K is the in... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.1.3.1 Bits-input to rectangular matrix | The bit sequence input to the Turbo code internal interleaver kx is written into the rectangular matrix as follows. (1) Determine the number of rows R of the rectangular matrix such that: ⎪⎩ ⎪⎨ ⎧ = ≤ ≤ ≤ ≤ ≤ ≤ = e) other valu any ( if 20, )) 530 481 ( or ) 200 160 (( if 10, ) 159 40 ( if 5, K K K K R where the rows of ... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.2 Intra-row and inter-row permutations | After the bits-input to the R×C rectangular matrix, the intra-row and inter-row permutations for the R×C rectangular matrix are performed by using the following algorithm: (1) Select a primitive root v from Table 6.1. (2) Construct the base sequence s(i) for intra-row permutation as: s(i) = [v × s(i - 1)] mod p, i = 1,... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.2.1 Bits-output from rectangular matrix with pruning | After intra-row and inter-row permutations, the bits of the permuted rectangular matrix are denoted by y'k: ⎥ ⎥ ⎥ ⎥ ⎦ ⎤ ⎢ ⎢ ⎢ ⎢ ⎣ ⎡ + − + − + + + + CR R C R C R R R R R R R y y y y y y y y y y y y ' ' ' ' ' ' ' ' ' ' ' ' ) 2 ) 1 (( ) 1 )1 (( 3 2 ) 2 2 ( ) 2 ( 2 ) 1 2 ( ) 1 ( 1 M K K M M M K K ETSI ETSI TS 102 721-3 V1.... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.2.2 Rate matching | The rate matching algorithm described below is used to adapt the number of bits at the output of the turbo encoder (which is three times the input block length in bits plus 12 bits for the encoder tails) to the available channel bits. If the CRC (see clause 5.1.1) is used, rate matching might become necessary in order ... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 6.3 Channel Interleaving | The channel interleaver is specified as the cascade of two separate channel interleavers. This allows to have the second interleaver always operating on a single frame. The first inteleaver will then take care of dispersing bits on the full PDCH data burst. The 1st interleaver can be implemented as a block interleaver ... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7 Spreading and Modulation | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.1 PDCH and PCCH spreading | Figure 7.1 illustrates the spreading and scrambling of the PDCH and PCCH. Spreading is applied after mapping the control and data binary values 0 and 1 to +1 and -1 respectively and before pulse shaping. It consists of two operations: 1) the channelization operation, which transforms every symbol into a number of chips... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.1.1 PDCH and PCCH channelization | The PCCH is spread by the channelization code Cch,c and the PDCH is spread by a different channelization codes, Cch,d. Symbols of both channels are BPSK-modulated. The channelization codes are Orthogonal Variable Spreading Factor (OVSF) codes that preserve the orthogonality between different physical channels (dedicate... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.1.2 PDCH and PCCH scrambling | The same scrambling solution is based on the one used in 3GPP WCDMA (long code option of 3GPP) [i.10]. However, differently from 3GPP the scrambling code period is not limited to 38 400 chips. In fact a period equal to the entire PDCH burst length (see clause 5.1) is selected to minimize code collision probability betw... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.2 Up-Link Burst Preamble | The preamble processing is illustrated in Figure 7.1. The ULB complex quaternary preamble p is composed as follows: p(k) = s1(k div Nc) s2(k mod Nc) k = 0, 1, 2, … P·Nc - 1 where the 'div' operator is the integer division and the 'mod' operator is the modulus operator 8 i.e. the rest of an integer division). The number... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.2.1 Sequence s1 | The sequence s1 is a quaternary sequence with period equal to 96 constructed by combining two real binary sequences into a complex one. Each of the two real sequences is constructed as the position-wise modulo 2 sum of P chip segments of two binary m-sequences generated by means of two generator polynomials of degree 9... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.2.2 Sequence s2 | The sequence s2 is of length 256, or 128 or 16 depending on the PDCH chip rate (3,94 Mchip/s, or 1,92 Mchip/s or 240 kchip/s respectively. We will assume that only a single s2 sequence is used in a given beam. If multiple preambles are required in a given beam to reduce the collision probability then this may be obtain... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.2.2.1 SF = 16 | The two sequences are obtained with weight [+j; +j; +j ; +j] and permutation [2; 1; 8; 4;]: Sequence 1 is: [1, j, j ,1, j, -1, -1, j, j, 1, -1, -j, 1, -j, j, -1], * exp(j π/4) Sequence 2 is: [1, j, -j, -1, j, -1, 1, -j, j, 1, 1, j, 1, -j, -j, 1] * exp(j π/4) ETSI ETSI TS 102 721-3 V1.2.1 (2013-08) 28 |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.2.2.2 SF = 128 | The two sequences are obtained with weight [+j; -1; +j; -1; j; -1; -1] and permutation [64; 1; 32; 4; 8; 2; 16]: Sequence 1 is: [+1, -1, -1, +1, -1, +1 ,+1 ,-1, +j, -j, +j, -j, +j, -j, +j, -j, -1, +1, -1, +1, +1, -1, +1, -1, -j, +j, +j, -j, -j, +j, +j, -j, +j, +j, -j, -j, +j, +j, -j, -j, -1, -1, -1, -1, +1, +1, +1, +1,... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.2.2.3 SF = 256 | The two sequences are obtained with weight [+j; +j; +j; +j; -1; +j; +j; -1] and permutation [16; 8; 4; 32; 2; 64; 1; 128]: Sequence 1 is: [+1, +j, -1, -j, +j, -1, -j,+1, +j, -1, -j,+1,+1, +j, -1, -j, +j, -1, -j,+1, -1, -j,+1, +j,+1, +j, -1, -j, -j,+1, +j, -1, +j, -1, +j, -1,+1, +j,+1, +j, -1, -j, - 1, -j, -j,+1, -j,+1,... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 7.3 Modulation | Modulation of the complex-valued chip sequence S generated by the spreading process described in clause 7.1 is shown below in Figure 7.4 for a given uplink frequency ω. S Im{S} Re{S} cos(ωt) Complex-valued chip sequence from spreading operations -sin(ωt) Split real & imag. parts Pulse- shaping Pulse- shaping Figure 7.4... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8 Radio transmission | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.1 Frequency bands and channel arrangement | The nominal channel spacing is either 5 MHz or 2,5 MHz or 325 kHz respectively for the 3,84 Mchip/s, 1,92 Mchip/s and 240 kchip/s. The terminal shall be able to transmit on any frequency signalled in the SCT table in TS 102 721-6 [1]. The granularity for the frequency signalled in the SCT is 100 Hz. |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.2 Stability and accuracy requirements | For stability the terminal shall be locked either on a satellite Forward-Link (FL) carrier or on a Down-Link (DL) carrier from a terrestrial repeater. ETSI ETSI TS 102 721-3 V1.2.1 (2013-08) 30 It is assumed here that the terminal will generate the Tx carrier and clock frequencies based on a reference locked on the rec... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.2.1 Frequency and symbol timing stability and accuracy | The modulated carrier frequency shall be accurate to within ±0,5 PPM observed over a period of one frame compared to the carrier frequency received from the satellite or a terrestrial repeater. The terminal shall use the same frequency source for both RF frequency generation and the chip clock. |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.2.2 Power stability and accuracy | The accuracy with which the output power is set shall be better than 2 dB. The terminal shall be able to set its output power in a range of 30 dB with monotonic steps of 0,5 dB from [Pmax -30 dB to Pmax]. When not transmitting, the output power shall be below -56 dBm. |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.3 Transmitter characteristics | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.3.1 Power output characteristics and power class | NOTE: Typical EIRP values are defined in TS 102 721-1 [i.11]. |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.3.2 Transmit polarization | |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.3.2.1 Satellite Access | Circular polarization shall be supported by vehicular terminals. Hand-held terminals, if allowed by the system operator may use linear polarization but QoS may be reduced with respect to vehicular terminals. ETSI ETSI TS 102 721-3 V1.2.1 (2013-08) 31 |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.3.2.2 Terrestrial Access | Linear polarization will be used by the CGC. This does not imply that vehicular terminals shall use an ad-hoc antenna for CGC (although this may improve the link budget as the optimal antenna patterns for satellite and terrestrial paths are different). |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.3.3 Unwanted emissions | Adjacent Channel Leakage power Ratio (ACLR) (defined as the ratio of the Square Root Raised Cosine (SRRC) filtered mean power centred on the assigned channel frequency to the SRRC filtered mean power centred on an adjacent channel frequency) shall be higher than 33 dB for the first adjacent channel slot and higher than... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.4 Transmit procedure | The following transmit procedure is foreseen. (1) The terminal randomly selects a preamble spreading code from the set of available spreading codes (if more than one is available). The random function shall provide a uniform distribution of the selected codes. (2) The terminal sets the transmit power in order to get an... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 8.5 Tx/Rx states | The terminal transmit/receive states are as follows: • Idle (terminal disabled or switched off). • Search (transmission disabled). • Satellite Rx synchronized status (transmission enabled upon reception of the SCT, SAT and SDT signalling tables, see [1]). • CGC Rx Synchronized status (transmission enabled upon receptio... |
44d83722354f2afbbe023c655bb25653 | 102 721-3 | 9 Physical layer measurements | Radio characteristics are measured and reported to higher layers and the network. Such measurements are for further study. ETSI ETSI TS 102 721-3 V1.2.1 (2013-08) 34 Annex A (informative): Generation of Complex Complementary Golay Codes The pair of complementary sequences can be generated by the following Haskell code:... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 1 Scope | The present document specifies interfaces between the ITS Security entity and the ITS Facilities layer including interface services and service primitives which are extensible in order to achieve general applicability. Additionally, it specifies related procedures and common parameters. The SF-SAP description in the pr... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 2 References | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 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... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 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... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 3 Definition of terms, symbols and abbreviations | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 665 [i.1], ETSI TS 102 940 [1] and the following apply: security association: addressing information and 'security material' for connecting to the 'security management entity' NOTE: This corresponds to 'enrolment authorities' and 'authorization au... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 3.2 Symbols | Void. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 302 665 [i.1], ETSI TS 102 940 [1] and the following apply: SAP Service Access Point SF-SAP Security entity - Facilities layer SAP ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 10 |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4 Architecture | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1 General | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1.1 Introduction | Figure 1 shows the ITS station reference architecture, as defined in ETSI EN 302 665 [i.1]. The present document contains the specification of the Service Access Points (SAP), connecting the security entity and the facilities layer, i.e. SF-SAP. Figure 1: ITS station reference architecture Interaction between the secur... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1.2 Vertical message flow | Figure 2 extends the ITS station reference architecture by illustrating the overall information flow through the layers, from originating application on the left hand side, to the receiving application on the right hand side. Figure 2: TX (left) and RX (right) information flow through the ITS station ETSI ETSI TS 102 7... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1.3 Horizontal control communication | Figure 4 outlines the second communication principle. There is a horizontal control communication between the security entity and the corresponding communications layer, facilities layer in this case. This is needed for the ID change functionality introduced later. In general, the security entity will be able to indica... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1.4 Protocol work split | The SF-SAP provides a set of primitive Security functions to the Facilities layer. Figure 5 shows how a protocol entity within the Facilities layer handles the sending and receiving of information but uses some security extensions to invoke the primitive functions of the Security entity in order to meet the security re... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1.5 Multiple instances | The present document does not discuss architecture. However, the SF-SAP can support different permissions. The management of different credential sets at the same time can be implemented by using multiple instances of the Security entity at the same time. Different or same components in the Facilities layer might use m... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.1.6 Error handling | The present document does not make assumptions on implementation specific error handling for using the described services. This means that, if a call of any of the described services fails for some reason, the present document does not specify if this should be handled using exceptions or any other error handling techn... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 4.2 Security services | The required ITS security services are identified as the first level security services in ETSI TS 102 940 [1], clause 5.2. In addition to those, security services used in the research projects PRE-DRIVE C2X and EVITA were adopted and fitted to the existing services. See PRESERVE Deliverable D1.3 [i.8] and [i.9] for doc... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.1 Interface services | The following services for the SF-SAP are defined in the present document: • SF-SIGN Create authentication information for outgoing ITS messages • SF-VERIFY Validate authentication information from incoming ITS messages • SF-ENCRYPT Encrypt outgoing ITS single messages • SF-DECRYPT Decrypt incoming ITS single messages ... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2 Service primitives and parameters | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.1 SF-SIGN | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.1.1 Description | The service adds authentication information to the message. Key and identity management is internal to the security entity. Format of the created security header is dependent on the selected security protocol. The key to use is expected to be selected by the key and identity management of the security entity. Neverthel... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.1.2 SF-SIGN.request | SF-SIGN.request is sent from the Facilities layer to the Security entity for executing the SIGN service. The parameters shall be as described in Table 2. Table 2: SF-SIGN.request Name Type Valid range Description Status tbs_message_length INTEGER 0 to 216 - 1 Length of the message to be signed Mandatory tbs_message OCT... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.1.3 SF-SIGN.confirm | SF-SIGN.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-SIGN.request. The parameters shall be as described in Table 3. Table 3: SF-SIGN.confirm Name Type Valid range Description Status sec_message_length INTEGER 0 to 216 - 1 Length of the signed message Mandatory sec_mess... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.2 SF-VERIFY | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.2.1 Description | The service verifies the validity of the digital signature and meta information contained in the security header. Its format, specification, and features are dependent on the selected security protocol. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.2.2 SF-VERIFY.request | SF-VERIFY.request is sent from the Facilities layer to the Security entity for executing the VERIFY service. The parameters shall be as described in Table 4. Table 4: SF-VERIFY.request Name Type Valid range Description Status sec_header_length INTEGER 0 to 216 - 1 Length of the security header Mandatory sec_header OCTE... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.2.3 SF-VERIFY.confirm | SF-VERIFY.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF- VERIFY.request. The parameters shall be as described in Table 5. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 16 Table 5: SF-VERIFY.confirm Name Type Valid range Description Status report INTEGER 0 to 28 - 1 VERIFY ret... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.3 SF-ENCRYPT | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.3.1 Description | This service encrypts message for specific recipients. The designated recipient has to be known to the security entity. Therefore, an identifier is required to indicate the recipient. An internal mapping of target_id to certificate_id shall be possible, to select the proper target key. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.3.2 SF-ENCRYPT.request | SF-ENCRYPT.request is sent from the Facilities layer to the Security entity for executing the ENCRYPT service. The parameters shall be as described in Table 6. Table 6: SF-ENCRYPT.request Name Type Valid range Description Status tbe_payload_length INTEGER 0 to 216 - 1 Length of the payload to be encrypted Mandatory tbe... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.3.3 SF-ENCRYPT.confirm | SF-ENCRYPT.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF- ENCRYPT.request. The parameters shall be as described in Table 7. Table 7: SF-ENCRYPT.confirm Name Type Valid range Description Status encrypted_message_length INTEGER 0 to 216 - 1 Length of the encrypted_message... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.4 SF-DECRYPT | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.4.1 Description | This services decrypts messages, which were encrypted using the ENCRYPT service. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.4.2 SF-DECRYPT.request | SF-DECRYPT.request is sent from the Facilities layer to the Security entity for executing the DECRYPT service. The parameters shall be as described in Table 8. Table 8: SF-DECRYPT.request Name Type Valid range Description Status encrypted_message_length INTEGER 0 to 216 - 1 Length of the encrypted_message Mandatory enc... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.4.3 SF-DECRYPT.confirm | SF-DECRYPT.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF- DECRYPT.request. The parameters shall be as described in Table 9. Table 9: SF-DECRYPT.confirm Name Type Valid range Description Status plaintext_message_length INTEGER 0 to 216 - 1 Length of the decrypted message... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.5 SF-IDCHANGE-SUBSCRIBE | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.5.1 Description | Subscription for notifications on IDCHANGE, used for concurrent identifiers exchange across the ITS-S. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 18 |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.5.2 SF-IDCHANGE-SUBSCRIBE.request | SF-IDCHANGE-SUBSCRIBE.request is sent from the Facilties layer to the Security entity for executing the IDCHANGE-SUBSCRIBE service. The parameters shall be as described in Table 10. Table 10: SF-IDCHANGE-SUBSCRIBE.request Name Type Valid range Description Status idchange_event_hook Not applicable in ASN.1 Not applicabl... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.5.3 SF-IDCHANGE-SUBSCRIBE.confirm | SF-IDCHANGE-SUBSCRIBE.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-IDCHANGE-SUBSCRIBE.request. The parameters shall be as described in Table 11. Table 11: SF-IDCHANGE-SUBSCRIBE.confirm Name Type Valid range Description Status subscription INTEGER 0 to 264 – 1 Subscript... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.6 SF-IDCHANGE-EVENT | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.6.1 Description | Indication for notifications on IDCHANGE, see SF-IDCHANGE-SUBSCRIBE specified in clause 5.2.5. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.6.2 SF-IDCHANGE-EVENT.indication | SF-IDCHANGE-EVENT.indication is sent from the Security entity to the Facilities layer for executing the IDCHANGE-EVENT service. The parameters shall be as described in Table 12. Table 12: SF-IDCHANGE-EVENT.indication Name Type Valid range Description Status command ENUMERATED PREPARE COMMIT ABORT DEREG Id-change phase,... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.6.3 SF-IDCHANGE-EVENT.response | SF-IDCHANGE-EVENT.response is sent from the Facilities layer to the Security entity as a corresponding reply to SF- IDCHANGE-EVENT.indication. The parameters shall be as described in Table 13. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 19 Table 13: SF-IDCHANGE-EVENT.response Name Type Valid range Description Status return... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.7 SF-IDCHANGE-UNSUBSCRIBE | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.7.1 Description | Unsubscription for IDCHANGE notifications, see SF-IDCHANGE-SUBSCRIBE specified in clause 5.2.5. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.7.2 SF-IDCHANGE-UNSUBSCRIBE.request | SF-IDCHANGE-UNSUBSCRIBE.request is sent from the Facilities layer to the Security entity for executing the IDCHANGE-UNSUBSCRIBE service. The parameters shall be as described in Table 14. Table 14: SF-IDCHANGE-UNSUBSCRIBE.request Name Type Valid range Description Status subscription INTEGER 0 to 264 - 1 Subscription han... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.7.3 SF-IDCHANGE-UNSUBSCRIBE.confirm | SF-IDCHANGE-UNSUBSCRIBE.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-IDCHANGE-UNSUBSCRIBE.request. The parameters shall be as described in Table 15. Table 15: SF-IDCHANGE-UNSUBSCRIBE.confirm Name Type Valid range Description Status (none) - - - - |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.8 SF-IDCHANGE-TRIGGER | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.8.1 Description | This service is needed in order to ask the Security entity to trigger IDCHANGE procedure. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.8.2 SF-IDCHANGE-TRIGGER.request | SF-IDCHANGE-TRIGGER.request is sent from the Facilities layer to the Security entity for executing the IDCHANGE-TRIGGER service. The parameters shall be as described in Table 16. Table 16: SF-IDCHANGE-TRIGGER.request Name Type Valid range Description Status (none) - - - - |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.