hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.1.3.7 Independence of other CC transactions. | The standard DECT rules apply regarding the use of Service Change CC operations and MM states. Service change CC operations related to the ULE PVC (transaction 5 FT initiated) are orthogonal to the states of other CC transactions that may exist in the PT-FT pair. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.1.3.8 Default MAC parameters for implicitly created MBC | When a pair of MAC MBCs is created without exchange of MAC signalling, as result of the procedure described in clause 12.1.3.1.2.2, case b), the following default MAC parameters shall be used. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 150 Table 58: Default MAC parameters in MBCs created without exchange of MAC messages a... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.1.3.9 Paging descriptors in suspend and resume states | Paging descriptors for BU paging configured by means of << ULE-MAC-CONFIGURATION-INFO >> apply even in NWK suspend state. Paging commands received over BU when the PP is in "NWK resumed" state trigger a MAC resume using expedited procedures as described in clause 10.10. Paging commands received over BU when the PP is i... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.1.3.10 Negotiation rules | The following negotiation rules apply when exchanging parameters via any CC Service Change operation: << ULE-MAC-CONFIGURATION-INFO >> The descriptors are always set by the FT. << TRANSIT-DELAY >>, <Overall MAC layer maximum lifetime> The initiating side may propose a new value. The other side may accept it, or reply w... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.2 Other NWK layer procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.2.1 Service call setup | The following text together with the associated clauses define the mandatory requirements with regard to the present document. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.2.1.1 Prerequisites | The service call shall be established only over a (circuit mode) basic MAC connection. The NWK messages associated to this call shall be routed over its own (basic connection) MBC. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.2.1.2 Procedure | The GAP outgoing call request procedure shall be used as defined in EN 300 444 [9], clause 8.2, with the following replacement to the {CC-SETUP} message. Table 59: Values used within the {CC-SETUP} message for service call Information element Field within the information element Standard values within the field/informa... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.2.2 Storing the Derived Cipher Key for CCM (DCK-CCM) | This procedure is required by the DLC Service [ULE1-D.12] "CCM/AES encryption". It is related, but not exactly the same, to the procedure "Storing the Derived Cipher Key (DCK)" (clause 8.27 of EN 300 444 (GAP) [9]). In order to generate a Derived Cipher Key for CCM, the authentication of PT procedure of the feature [UL... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3 Terminal capabilities and FP broadcasts | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3.1 Terminal capability indication | The PP shall be able to send the <<Terminal capability>> information element and the FP shall be able to receive it at least in {ACCESS-RIGHTS-REQUEST} and when location registration is supported in the {LOCATE-REQUEST}. The following text together with the associated clauses define the mandatory requirements with rega... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3.2 FP broadcasts | NOTE: This clause defines only the NWK layer content in the FP broadcast. See also clause 10.3.2.2.1 which defines the MAC layer content. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3.2.1 Higher layer information FP broadcast | The FP and PT shall support the broadcast of Higher Layer capabilities as part of QT MAC broadcast messages (see clause 10.3.2.2). The broadcast attributes are a small set of NWK layer and DLC layer capabilities (jointly known as "higher layer capabilities") that shall be broadcast regularly as part of the MAC layer br... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3.2.1.1 Higher layer information in standard FP broadcast (Qh = 3) | The Higher Layer capabilities Fixed Part Information field shall be used to indicate the support of the indicated features. Most bits are not specific of ULE part 1, but will be set in most RFPs due to the coexistence with voice services. Table 63: Higher layer information attributes in standard FP broadcast (Qh = 3) B... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3.2.1.2 Higher layer information in Extended FP broadcast (Qh = 4) | No Extended higher layer capabilities bits are used by the present document. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 12.3.2.1.3 Extended Higher Layer capabilities part 2 (Qh = 11) | The Extended Higher Layer capabilities, part 2, Fixed Part Information field shall be used indicating the support of ULE part 1 (bit < a39 >) as well as other services and optional features that may be supported by the RFP. Table 64: Extended Higher Layer Capabilities part 2 interpretation by the PP BIT Number Attribut... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13 Services and Interworking procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13.1 Interworking specific procedures | The different types of Interworking options supported by the present document are listed and described in annex B (normative). The U-plane and C-plane procedures that are specific for each Interworking type are defined in the applicable clause of annex B. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13.2 Other Interworking procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13.2.1 Transport of IWU-to-IWU data | This procedure may be used to transport data between ULE applications peer-to-peer (i.e. FP to PP) in both directions. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13.2.1.1 General requirements | The transport of data shall take place over a ULE Service Call. The ULE Service Call Setup procedure shall be used to establish the call (see clause 12.2.1). At the end of the data transport the PP shall release the ULE Service Call procedure (see clause 8.7 of EN 300 444 [9]). |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13.2.1.2 Prerequisites | A ULE Service Call shall exist prior to attempting to transport data using this procedure. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 13.2.1.3 Procedure | Data shall be sent using an <<IWU-to-IWU>> Information Element contained within an IWU-INFO call control message. The general format of the <<IWU-to-IWU>> message is shown in clause A.3. The actual payload data for this message is defined on a ULE Application Protocol specific basis, and is not defined in the present d... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 1 Scope | The present document specifies the protocol conformance testing in TTCN to ensure eCall NAD conformance when accessing a Universal Telecommunication System (UMTS) mobile network. The following TTCN test specification and design considerations can be found in the present document: - the testing architecture; - the test ... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 2 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... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 122 101: "Universal Mobile Telecommunications System (UMTS); LTE; Service aspects; Service principles (3GPP TS 22.101)". [2] ETSI TS 126 269: "Digital cellular telecommunications system (Phase 2+); Universal Mobile... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Directive 1999/5/EC of the European Parliament and of the Council of 9 March 1999 on radio equipment and telecommunications terminal equipment and the... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 3 Definitions and abbreviations | |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 121 905 [i.2] and the following apply: eCall: manually or automatically initiated emergency call, (TS12) from a vehicle, supplemented with a minimum set of emergency related data (MSD), as defined under the EU Commission's eSafety initiativ... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 121 905 [i.2] and the following apply: ATS Abstract Test Suite IVS In Vehicle System (eCall terminal and associated sub-systems in vehicle) NAD Network Access Device ETSI ETSI TS 102 936-2 V1.1.1 (2011-04) 8 |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 4 Requirements on the TTCN development | A number of requirements are identified for the development and production of TTCN specification for 3GPP UE at Uu interface. 1. Top-down design, following TS 134 123-1 [4], TS 134 108 [6] and TS 134 109 [3]. 2. A unique testing architecture and test method for testing all protocol layers of UE. 3. Uniform TTCN style a... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 5 ATS structure - Modularity | The eCall ATS is developed making use of the modular TTCN approach used for the development of the 3GPP ATS specifications. The following modules are used: BasicM, RRC_M, L3M, NAS_M, HSR5_R6_M, R7_M and R8_M. The module structure is shown in figure 1. ETSI ETSI TS 102 936-2 V1.1.1 (2011-04) 9 BasicM L3M RRC_M NAS_M eCa... |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 6 Test method and testing architecture | The test method and testing architecture is described in TS 134 123-3 [5], clauses 6.1 and 6.2. For the eCall ATS, the NAS test method and architecture is used as described in TS 134 123-3 [5], clause 6.3. |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 7 PCO and ASP definitions | The test PCO and ASP definitions are described in TS 134 123-3 [5], clause 7. |
12c213fc276c8a7f169833dfeafd75cb | 102 936-2 | 8 Design Considerations | The eCall test cases for UTRAN have been designed following the same principles used for other 3GPP UTRAN test cases. These can be found in TS 134 123-3 [5], clause 8. ETSI ETSI TS 102 936-2 V1.1.1 (2011-04) 10 Annex A (normative): Abstract Test Suite (ATS) The ATS has been produced using the Tree and Tabular Combined ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 1 Scope | The present document contains the stage 3 specification for the mIa, dIa and mId reference points of the M2M architecture as identified in TS 102 690 [2]. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 8601: "Data elements and interchange formats -- Information interchange -- Representation of dates and times". [2] ETSI TS 102 690: "Machine-to-Machine communications (M2M); Functional architecture". [3] ETSI TS 102 67... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 102 725: "Machine-to-Machine communications (M2M); Definitions". [i.2] IETF draft-yegin-coap-security-options-00: "CoAP Security Options". NOT... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 3 Definitions, symbols, abbreviations and conventions | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 102 725 [i.1] apply. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 3.2 Symbols | For the purposes of the present document, the symbols given in TR 102 725 [i.1] and the following apply: | Concatenation |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 102 725 [i.1] apply. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 3.4 Conventions | All data variables in the present document are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bitstring. The symbols " in a formula are used to indicate a null-terminated constant oc... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 4 Overview | The M2M system is resource based and the API uses the RESTful approach. Operation on resource among Applications and SCLs and between SCL instances are supported by means of Methods, Methods constitute the communication on the mIa, dIa and mId APIs. Each method conveys a set of information defined as Method Attributes.... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5 General security aspects | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1 Key provisioning and hierarchy derivation | The ETSI M2M key hierarchy is defined in TS 102 690 [2], clause 8. The following clauses describe the derivation procedures of the hierarchy. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1.1 Kmr provisioning | The M2M Service Root key (Kmr) shall have a length equal to 256 bits. Kmr may be provisioned offline (i.e. prior to the initial communication between D/G M2M Node and Network M2M Node or MSBF) into D/G M2M Node or UICC card. Kmr may be provisioned online (i.e. during the initial communication between D/G M2M Node and N... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1.1.1 Kmr provisioning independent of access network credentials | If IBAKE based bootstrapping carried using EAP over PANA is applied, then Kmr shall be provisioned as per the procedure described in clause 6.3.1.2. If TLS based bootstrapping carried using EAP over PANA is applied, then Kmr shall be provisioned as per the procedure described in clause 6.3.1.3. If TLS based bootstrappi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1.1.2 Kmr provisioning based on access network credentials | If GBA based bootstrapping is applied, then Kmr shall be provisioned as per the procedure described in clause 6.2.1. If EAP based bootstrapping using SIM/AKA access network credentials is applied, then Kmr shall be provisioned as per the procedure described in clause 6.2.2. If bootstrapping using EAP-based network acce... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1.1.3 Kmr refresh and invalidation | Kmr may be refreshed via a new manual pre-provisioning or via the invocation of a new bootstrapping procedure using either of the procedures listed in clauses 5.1.1.1 and 5.1.1.2, and the referenced clauses therein. Kmr may be invalidated based on M2M Service Provider policy. ETSI ETSI TS 102 921 V1.3.1 (2014-09) 29 |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1.2 Kmc derivation | The M2M Service Connection key (Kmc) shall have a length equal to 256 bits. Kmc shall be associated to a specific M2M Service Connection and shall be derived only upon successful mutual authentication between the D/G M2M Node and the Network M2M Node, using either of the methods described below. Kmc may be used for sec... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.1.2.4 Kmc refresh and invalidation | The Kmc key shall only be refreshed with every new mutual authentication and key agreement procedure. Kmc may be invalidated based on M2M Service Provider policy. Kmc shall be invalidated upon invalidation of the parent Kmr key. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 5.2 Security Assumptions | In the following text, entity A has "authenticated" entity B if entity A has a degree of confidence (appropriate to the sensitivity of the resources that can be acted on by messages from entity) that messages claiming to be from entity B were sent by entity B and messages sent to entity B are observed only by entity B.... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6 M2M Service Bootstrapping | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.1 General Principles | TS 102 690 [2] provides a variety of options for M2M service bootstrapping, some of which rely on mechanisms that are not included in of the present specification. Therefore, the M2M bootstrap procedures described in this clause are all optional to implement and use on both the M2M core side and the M2M Device/Gateway ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.2.1 GBA-based M2M Service Bootstrap Procedure | As described in clause 8.3.2.1 of TS 102 690 [2], the GBA-based M2M service bootstrap shall start with the D/G M2M Node and the BSF carrying out GBA bootstrapping over the Ub interface. There are two modes of GBA: ME-based (GBA_ME) and UICC-based (GBA_U). The latter requires that the UICC is GBA aware. The BSF shall de... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.2.1.1 Optional use of GBA_U with Ks_int_NAF | If the HTTP client is implemented in the UICC, Ks_int_NAF shall be used as Kmr. This option is recommended because if Ks_ext_NAF or Ks_NAF are used as a password in the HTTP digest calculation (see clause 6.2.1.2), then they could be exposed to malicious applications in the device environment at any time, while Ks_int_... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.2.1.2 HTTP Digest Authentication and bootstrap parameter delivery | Figure 6.1 shows the HTTP Digest Authentication procedure with the following sub-steps: Step 2.1 The D/G M2M Node shall send an HTTP POST request to the MSBF/NAF. It shall indicate to the MSBF/NAF that it supports 3GPP-bootstrapping based HTTP Digest authentication by including a "product" token to the "User-Agent" hea... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.2.1.3 M2M Root Key (Kmr) derivation | If GBA_ME is run, Ks_NAF as derived by the D/G M2M Node and the BSF shall be used as the M2M Root key (Kmr): • Ks_NAF = KDF (Ks, "gba-me", RAND, IMPI, NAF_Id). ETSI ETSI TS 102 921 V1.3.1 (2014-09) 32 If GBA_U is run, two NAF-specific keys are derived: • Ks_ext_NAF = KDF(Ks, "gba-me", RAND, IMPI, NAF_Id). • Ks_int_NAF ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.2.3 Bootstrapping from EAP-based access network layer | This procedure is based on utilizing the network access authentication procedure for bootstrapping the D/G M2M Node with the M2M service. Instead of authenticating the D/G M2M Node twice (once for the network access service, and another for the M2M service), the D/G M2M Node is authenticated once during the network acc... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3 Bootstrapping using other methods | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1 Bootstrapping methods using EAP over PANA | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.1 Generic procedure | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.1.1 Bootstrapping | EAP/PANA can be used by the D/G M2M Node and the Network M2M Node for performing M2M Service Bootstrapping procedure. This procedure registers the D/G M2M Node with a Network M2M Node by performing end-point authentication/authorization, M2M bootstrapping related parameter discovery, and key agreement. The following de... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.1.2 Bootstrap-Erase | The Erase procedure may be used when either the D/G M2M Node or the network desires to terminate the M2M service provided to the D/G M2M Node by the M2M Service Provider. A Bootstrap procedure followed by an erase procedure puts the D/G M2M Node back to its state prior to the bootstrapping with respect to the given M2M... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.2 EAP/PANA - IBAKE bootstrapping operations | If Identity Based Authenticated Key Exchange (IBAKE) as per EAP-IBAKE [48] and RFC 6267 [42] is used for performing service bootstrapping independently of access network credentials for D/G M2M Node, then the procedures defined in this clause shall be used. The IBAKE bootstrapping procedure shall be executed between D/... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.2.1 Provisioning of IBE specific parameters | In order for D/G M2M Node and MSBF to execute EAP-IBAKE [48], they shall be provisioned with two sets of parameters. The first set parameters shall be provisioned at the manufacture, and it consists of publicly known mutually agreed-to parameters. The second set includes individual private parameters known only to thei... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.2.2 Secure IBAKE protocol | The IBAKE protocol shall be executed between the D/G M2M Node and the MSBF via the authorized Network M2M Node. IBAKE messages shall be carried using EAP as the EAP-IBAKE method [48]. The EAP messages shall be transported over the mId interface using PANA [33]. The MSBF shall act as the EAP server, the Network M2M Node... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.1.3 EAP-TLS over PANA | If TLS-based authentication is desired with EAP/PANA, then EAP-TLS as per RFC 5216 [34] shall be used. EAP-TLS shall be transported over EAP/PANA just like any other EAP method as described in clause 6.3.1. Furthermore, ETSI M2M TLS/certificate-specific details are covered in clause 6.3.3. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.2 M2M Service Bootstrap Procedure using TLS over TCP | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.2.1 Recap of M2M Service Bootstrap Procedure using TLS over TCP | The architecture level details for M2M Service Bootstrap Procedure using TLS over TCP are specified in clause 8.3 of TS 102 690 [2], noting that clause 8.3.3.5 of TS 102 690 [2] provides the details in common with the M2M Service Bootstrap Procedure using EAP-TLS. This clause provides an overview of the description in ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.2.2 Pre-Provisioning for M2M Service Bootstrap Procedure using TLS over TCP | NOTE: Clause 8.3.3.5.2 of TS 102 690 [2] describes the credentials to be pre-provisioned to the D/G. The M2M Device/Gateway certificates shall conform to the specification in clause 6.3.3.3.1.1. The MSBF certificates shall conform to the specification in clause 6.3.3.3.2.1. TLS support requirements are specified in cla... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.3.1 Introduction | The architecture for TLS/Certificate-Based M2M Service Bootstrap procedures is described in clause 8.3.3.5 of TS 102 690 [2]. These TLS/Certificate-Based M2M Service Bootstrap Procedures are the procedure using EAP-TLS over PANA (clause 6.3.1.3) and the procedure using TLS over TCP (clause 6.3.2). ETSI ETSI TS 102 921 ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.3.2 TLS Details for TLS/Certificate-Based M2M Service Bootstrap Procedures | The bulk encryption algorithm for TLS (in these M2M Service Bootstrap procedures) shall use 256-bit encryption keys. The following TLS Versions are supported for these M2M Service Bootstrap procedures: • TLS v1.2 (RFC 5246 [35]) with the following TLS Cipher suites: - TLS_RSA_WITH_AES_128_CCM [74] with client-certifica... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.3.3 Certificate Considerations | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.3.3.1 M2M Device/Gateway Certificate Considerations | 6.3.3.3.1.1 M2M Device/Gateway Certificate Specifications NOTE 1: The M2M Device/Gateway certificate is used by the MSBF to authenticate D/G-M2M-Nodes instantiated in the M2M Device/Gateway with which the certificate is associated. The M2M Device/Gateway certificate shall be pre-provisioned by the M2M Device/Gateway Ma... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.3.3.3.2 MSBF Certificate Considerations | 6.3.3.3.2.1 MSBF Certificate Specifications NOTE 1: The MSBF certificate is used by the D/G-M2M-Node to authenticate the MSBF as part of the TLS handshake. The MSBF certificate shall have a certificate chain back to a TTP Root CA certificate or TTP Intermediate CA certificate present in the Security Environment Domain ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.1 Overview | The M2M Service Bootstrap Parameter Delivery Procedures is used to securely deliver M2M Service Bootstrap Parameters from the MSBF to the D/G M2M Node, upon request from the D/G M2M Node, as part of the following M2M Service Bootstrap procedures: • M2M Service Bootstrap procedure using GBA (clause 6.2.1). • M2M Service... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.2 bootstrapParamSet Resource | NOTE: The only management procedure applicable to the bootstrapParamSet resource is the execute method, and consequently, the only message that can contain a bootstrapParamSet resource is a response primitive. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.2.1 bootstrapParamSet Resource URI | The URI of the bootstrapParamSet resource shall be of the form: • <MSBF-FQDN> "/bootstrapParamSet". where: • <MSBF-FQDN> This is the FQDN of the MSBF. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.2.2 bootstrapParamSet Resource Attributes | The bootstrapParamSet resource shall contain the attributes in table 6.4. The format of these attributes shall conform to clauses 11.5 and 12.2. Table 6.4: bootstrapParamSet Resource Attributes AttributeName Mandatory/Optional Description securityM2MNodeId M M2M-Node-ID assigned by the MSBF to the D/G M2M Node. See tab... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.3 M2M Service Bootstrap Parameter Delivery Procedure Primitives | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.3.1 bootstrapParamSetExecuteRequestIndication | This request is used by the D/G M2M Node to request the MSBF to provide Service Bootstrap Parameters to the D/G M2M Node. The primitive shall comply with table 6.5. The format of the primitive attributes shall conform to clauses 11.6 and 12.3. ETSI ETSI TS 102 921 V1.3.1 (2014-09) 51 Table 6.5: bootstrapParamSetExecute... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.3.2 bootstrapParamSetExecuteResponseConfirm (successful case) | This primitive confirms the establishment of an M2M Root Key (Kmr), and includes a resource that contains the parameters associated with the established M2M Service Bootstrap. The primitive shall comply with table 6.6. The format of the primitive attributes shall conform to clause 11.6. Table 6.6: bootstrapParamSetExec... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 6.4.3.3 bootstrapParamSetExecuteResponseConfirm (unsuccessful case) | The bootstrapParamSetExecuteRequestIndication primitive triggers this response. The primitive shall comply with table 6.7. The format of the primitive attributes shall conform to clause 11.6. Table 6.7: bootstrapParamSetExecuteResponseConfirm (unsuccessful case) bootstrapParamSetExecute Primitive: bootstrapParamSetExec... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7 M2M Service Connection Procedures | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.1 General principles | The use of an M2M Service Connection Procedure described in the present document is optional. If an M2M Service Connection procedure is not used, then access network security clause 8.1 shall be used for mId Security. Whether or not M2M Service Connection is required for the communication is pre-configured in the D/G M... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.2.1 M2M Service Connection Procedure based on GBA | As described in clause 8.4.4 of TS 102 690 [2], the GBA-based M2M Service Connection procedure shall start with the D/G M2M Node and the BSF carrying out GBA bootstrapping over the Ub interface. There are two modes of GBA: ME-based (GBA_ME) and UICC-based (GBA_U). The latter requires that the UICC is GBA aware. The BSF... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.2.1.1 TLS-PSK with GBA bootstrapped security association | The M2M Device/Gateway and the Network M2M Node may use the GBA security association to set up a TLS tunnel. clause 5.3.3 of TS 124 109 [5] defines the TLS-PSK based implementation of bootstrapped security association usage over the Ua interface. When the D/G M2M Node initiates the TLS handshake, it shall indicate to t... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.2.1.1.1 M2M Connection Key (Kmc) derivation | If GBA_ME is run, Ks_NAF as derived by the D/G M2M Node and the BSF shall be used as the M2M Connection Key (Kmc): • Ks_NAF = KDF (Ks, "gba-me", RAND, IMPI, NAF_Id). If GBA_U is run, two keys are derived: • Ks_ext_NAF = KDF(Ks, "gba-me", RAND, IMPI, NAF_Id). • Ks_int_NAF = KDF(Ks, "gba-u, RAND, IMPI, NAF_Id). In this c... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.3 M2M Service Connection Procedures using EAP/PANA | This clause describes the M2M Service Connection Setup and Tear-down Procedures using EAP/PANA. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.3.1 M2M Service Connection Setup Procedure using EAP/PANA | EAP/PANA shall be used by the D/G M2M Node and the Network M2M Node for performing M2M Service Connection Setup procedure. This procedure connects the D/G M2M Node to a Network M2M Node by performing end-point authentication/authorization, parameter discovery, and key agreement. EAP [22] shall be used for mutual authen... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.3.2 M2M Service Connection Tear-down Procedure using EAP/PANA | The M2M Service Connection Tear-down Procedure may be used for tearing down an M2M Service Connection between the D/G M2M Node and the Network M2M Node. PANA Termination Procedure [33] shall be used for this purpose. Either the D/G M2M Node or the Network M2M Node may initiate the procedure. The entity that desires to ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4 M2M Service Connection Procedure based on TLS-PSK | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.1 Introduction | Clause 7.4.2 of the present document specifies the details for D/G M2M Nodes and MAS that support The M2M Service Connection procedure based on TLS-PSK. The following details are provided herein: • TLS details. • Sequence of events. • Parameter delivery to D/G M2M Node. • M2M Service Connection Parameter Delivery Proce... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.1 Overview | The M2M Service Connection Parameter Delivery Procedure is used to deliver M2M Service Connection Parameters (as part of an M2M Service Connection Procedure based on TLS-PSK) from the MAS to the D/G M2M Node, upon request from the D/G M2M Node. The description to this procedure utilizes the mapping of primitives descri... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.2 connectionParamSet Resource | The only management procedure applicable to the connectionParamSet resource is the execute method, and consequently, the only message that may contain a connectionParamSet resource is a response primitive. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.2.1 connectionParamSet Resource URI | The URI of the connectionParamSet resource shall be of the form: • <MAS-FQDN> "/connectionParamSet" where: <MAS-FQDN> This shall be the FQDN of the MAS that is either pre-configured on the D/G M2M Node or established during an M2M Service Bootstrap Procedure. |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 7.4.5.2.2 connectionParamSet Resource Attributes | The connectionParamSet resource shall contain the attributes in table 7.1. The format of these attributes shall conform to clauses 11.5 and 12.2. ETSI ETSI TS 102 921 V1.3.1 (2014-09) 63 Table 7.1: connectionParamSet Resource Attributes AttributeName Mandatory/Optional Description securityConnectionId M M2M-Connection-... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.