ETSI TS 129 139-2017 Universal Mobile Telecommunications System (UMTS) LTE 3GPP system - fixed broadband access network interworking Home (e)Node B - security gateway interface (V1.pdf

1、 ETSI TS 129 139 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; 3GPP system - fixed broadband access network interworking; Home (e)Node B - security gateway interface (3GPP TS 29.139 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 139 V14.0.0 (2017-04)1

2、3GPP TS 29.139 version 14.0.0 Release 14Reference RTS/TSGC-0429139ve00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture

3、de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modif

4、ied without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Us

5、ers of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please sen

6、d your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission

7、 of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETS

8、I logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 139 V

9、14.0.0 (2017-04)23GPP TS 29.139 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, an

10、d can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the

11、 ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Fore

12、word This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the cor

13、responding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “ca

14、nnot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 139 V14.0.0 (2017-04)33GPP TS 29.139 version 14.0.0 Rele

15、ase 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 General . 6g34.1 Protocol Stack 6g34.1.1 Control Plane for H(e)NB SeGW 6g34.1.2 User Plane

16、 for H(e)NB SeGW . 7g35 Supporting QoS 8g35.1 General . 8g35.2 H(e)NB procedures. 8g35.2.1 General 8g35.2.2 QCI mapping 8g35.2.3 Reflective QoS 8g35.3 SeGW procedures . 8g36 Tunnel Management . 8g36.1 General . 8g36.2 H(e)NB procedures. 9g36.2.1 Tunnel establishment 9g36.2.1.1 IP address allocation

17、 9g36.2.1.2 NAT Traversal 9g36.2.1.3 H(e)NB NATed Tunnel-IP address discovery 9g36.2.2 Tunnel modification 9g36.2.3 Tunnel disconnection 9g36.3 SeGW procedures . 9g36.3.1 Tunnel establishment 9g36.3.1.1 IP address allocation . 9g36.3.1.2 NAT Traversal 10g36.3.1.3 H(e)NB NATed Tunnel-IP address disc

18、overy 10g36.3.2 Tunnel modification 10g36.3.3 Tunnel disconnection 10g37 PDUs and parameters specific to the present document 10g37.1 IETF RFC coding information defined within present document 10g37.1.1 IKEv2 Configuration Payloads attributes . 10g37.1.1.1 EXTERNAL_SOURCE_IP4_NAT_INFO attribute . 1

19、0g3Annex A (informative): Change history . 12g3History 13g3ETSI ETSI TS 129 139 V14.0.0 (2017-04)43GPP TS 29.139 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to conti

20、nuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 pre

21、sented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial o

22、nly changes have been incorporated in the document. ETSI ETSI TS 129 139 V14.0.0 (2017-04)53GPP TS 29.139 version 14.0.0 Release 141 Scope The present document specifies the H(e)NB SeGW interface. The interface is used for the interworking between a 3GPP system and a Fixed Broadband Access network d

23、efined by Broadband Forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a Fixed Broadband Access network as specified in 3GPP TS 23.139 2. The specification covers the QoS aspects and Tunnel management procedures. 2 References The following documen

24、ts contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For

25、 a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Speci

26、fications“. 2 3GPP TS 23.139: “3GPP System-Fixed Broadband Access Network Interworking; Stage 2“. 3 3GPP TS 24.139: “3GPP System-Fixed Broadband Access Network Interworking; Stage 3“. 4 IETF RFC 2474 (December 1998): “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 He

27、aders“. 5 IETF RFC 5996: “ Internet Key Exchange Protocol Version 2 (IKEv2)“. 6 IETF RFC 3948: “UDP Encapsulation of IPsec ESP Packets“. 7 3GPP TS 33.320: “Security of Home Node B (HNB) / Home evolved Node B (HeNB)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present doc

28、ument, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. H(e)NB Reflective QoS function: H(e)NB Reflective QoS function is a H(e)NB function in order to support

29、 QoS for uplink traffic over a Fixed Broadband Access network as specified in 3GPP TS 23.139 2. H(e)NB local IP address Info: H(e)NB local IP address Info is defined as either the public IPv4 address or IPv6 address assigned to the H(e)NB by the Fixed Broadband Access Network domain, or the public I

30、Pv4 address and the UDP port number used by the NATed RG that is used for this H(e)NB. The public IPv4 address used by the NATed RG is assigned by the Fixed Broadband Access Network domain. ETSI ETSI TS 129 139 V14.0.0 (2017-04)63GPP TS 29.139 version 14.0.0 Release 143.2 Abbreviations For the purpo

31、ses of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. DSCP Differentiated Services Code Point H(e)NB Home (e)NodeB NAT Network

32、 Address Translation NAT-T NAT Traversal SeGW Security Gateway4 General 4.1 Protocol Stack 4.1.1 Control Plane for H(e)NB SeGW UDP L2 L1 IPv4 H(e)NBSeGWIKEv2 NAT UDP L2 L1 IPv4 IKEv2 L2 L1 IPv4 L2 L1 IPv4 UDP UDP Legend: - IKEv2 Protocol: This protocol is used to between H(e)NB and SeGW. The IKEv2 p

33、rotocol is defined in IETF RFC 5996 5. Figure 4.1.1-1: Control Plane for H(e)NB - SeGW Interface over IPv4 transport network ETSI ETSI TS 129 139 V14.0.0 (2017-04)73GPP TS 29.139 version 14.0.0 Release 14H(e)NBSeGWUDP L2 L1 IPv6 IKEv2 UDP L2 L1 IPv6 IKEv2 Legend: - IKEv2 Protocol: This protocol is u

34、sed to between H(e)NB and SeGW. The IKEv2 protocol is defined in RFC 5996 5. Figure 4.1.1-2: Control Plane for H(e)NB - SeGW Interface over IPv6 transport network 4.1.2 User Plane for H(e)NB SeGW H(e)NB SeGWNAT L2 L1 IPv4 L2 L1 IPv4 UDP UDP L2 L1 IPv4 UDP Payload IPsec L2 L1 IPv4 UDP Payload IPsec L

35、egend: - UDP: UDP encapsulation is used if NAT is detected between the H(e)NB and the SeGW. Figure 4.1.2-1: User Plane for H(e)NB - SeGW Interface over IPv4 transport network H(e)NBSeGWIPsec L2 L1 IPv6 Payload IPsec L2 L1 IPv6 Payload Figure 4.1.2-2: User Plane for H(e)NB - SeGW Interface over IPv6

36、transport network ETSI ETSI TS 129 139 V14.0.0 (2017-04)83GPP TS 29.139 version 14.0.0 Release 145 Supporting QoS 5.1 General At interworking with a Fixed Broadband Access network, QoS is provided by DSCP marking as specified in IETF RFC 2474 4. 5.2 H(e)NB procedures 5.2.1 General The H(e)NB shall s

37、upport DSCP marking on the IPsec header when forwarding the UE uplink traffic. Based on H(e)NB configuration either the QCI mapping or the Reflective QoS may be used. 5.2.2 QCI mapping The QCI mapping table contains a one-to-one mapping from QCI value to DSCP marking value. The QCI mapping table is

38、configured in the H(e)NB by the operator. When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the QCI mapping table based on the QCI value of the EPS bearer/PDP context before the IPsec tunnel encapsulation. The H(e)NB shall set the DSCP marking value of the IPsec header accord

39、ing to the matched QCI mapping table entry. 5.2.3 Reflective QoS To support the H(e)NB Reflective QoS function for uplink traffic, the H(e)NB shall create and maintain the uplink DSCP marking rules for each active PDN connection as specified for UE Reflective QoS function in 3GPP TS 24.139 3. When f

40、orwarding an uplink IP packet, the H(e)NB shall perform a lookup in the DSCP marking table based on the n-tuple of the IP header before the IPsec tunnel encapsulation. If a matching entry is found, the H(e)NB shall set the DSCP marking value of the IPsec header according to the matched DSCP marking

41、rule. If no matching entry is found, the H(e)NB shall copy the DSCP field of the outer IP header into the IPsec header before forwarding to the SeGW. 5.3 SeGW procedures When receiving a downlink data packet, the SeGW shall copy the DSCP marking value from the outer IP header into the IPsec header b

42、efore forwarding to the H(e)NB using the IPsec tunnel, as specified in 3GPP TR 23.139 2. 6 Tunnel Management 6.1 General The tunnel is an IPsec tunnel established via an IKEv2 protocol exchange IETF RFC 5996 5 between the H(e)NB and the SeGW which is through the Fixed Broadband Access Network. In an

43、 IPv4 Fixed Broadband Access Network, NAT can be deployed between the H(e)NB and the SeGW, e.g. in a Residence Gateway. A H(e)NB behind the NAT shall invoke the NAT traversal procedure for IKEv2. The IPsec tunnel is encapsulated over UDP in the Tunnel-Mode as specified in IETF RFC 5996 5. ETSI ETSI

44、TS 129 139 V14.0.0 (2017-04)93GPP TS 29.139 version 14.0.0 Release 146.2 H(e)NB procedures 6.2.1 Tunnel establishment 6.2.1.1 IP address allocation The SeGW shall provide the IP address to the H(e)NB for the communication with the EPC network. For dynamic IP address allocation, the H(e)NB shall incl

45、ude the requested IP address type (IPv4 address or IPv6 address) that needs to be configured in an IKEv2 CFG_REQUEST Configuration Payload in the IKE_AUTH request message as defined in IETF RFC 5996 5 after reception of the IKE_SA_INIT response from the SeGW. 6.2.1.2 NAT Traversal NAT can be deploye

46、d in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 5 shall be supported by H(e)NB. If NAT is detected between the H(e)NB and SeGW, the following procedures shall be performed: - UDP-Encapsulated ESP as defined in IETF RFC 5996 5; - sending the

47、 NAT-keepalive packet to keep NAT mapping alive if no other packet to the SeGW has been sent in M seconds as defined in the IETF RFC 3948 6; NOTE: M is a locally configurable parameter with a default value of 20 seconds as defined in the IETF RFC 3948 6. 6.2.1.3 H(e)NB NATed Tunnel-IP address discov

48、ery If NAT is detected between the H(e)NB and SeGW, the H(e)NB shall request the SeGW to return the H(e)NB local IP address information by including the EXTERNAL_SOURCE_IP4_NAT_INFO attribute as defined in subclause 7.1.1.1 in the CFG_REQUEST Configuration Payload within the IKE_AUTH request message

49、 The length field of the attribute shall be set to zero. The NATed IPv4 Address field and UDP Port number field shall be absent. If the H(e)NB subsequently receives the EXTERNAL_SOURCE_IP4_NAT_INFO attribute in the CFG_REPLY configuration payload from the SeGW, the H(e)NB shall report the IP address received in EXTERNAL_SOURCE_IP4_NAT_INFO attribute as the H(e)NB local IP address to the MME/SGSN. 6.2.2 Tunnel modification NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local