Features and Functionality
IPSec for LTE/SAE Networks
Encryption Algorithms
HMAC Functions
Diffie-Hellman Groups
Dynamic Node-to-Node IPSec Tunnels
ACL-based Node-to-Node IPSec Tunnels
Traffic Selectors
Authentication Methods
X.509 Certificate-based Peer Authentication
| Step | Description |
|---|---|
|
1.
|
The peer node initiates
an IKEv2 exchange with the local node, known as the IKE_SA_INIT
exchange, by issuing an IKE_SA_INIT Request to
negotiate cryptographic algorithms, exchange nonces, and perform
a Diffie-Hellman exchange with the local node.
|
|
2.
|
The local node responds with an IKE_SA_INIT Response by choosing a cryptographic suite from the initiator’s offered choices, completing the Diffie-Hellman and nonce exchanges with the peer node. In addition, the local node includes the list of CA certificates that it will accept in its CERTREQ payload. For successful peer authentication, the CERTREQ payload must contain at least one CA certificate that is in the trust chain of the peer certificate. At this point in the negotiation, the IKE_SA_INIT exchange is complete and all but the headers of all the messages that follow are encrypted and integrity-protected. |
|
3.
|
The peer node initiates
an IKE_AUTH exchange with the local node by including the
IDi payload, setting the CERT payload to the peer certificate, and
including the AUTH payload containing the signature of the previous
IKE_SA_INIT Request message (in step 1) generated using
the private key of the peer certificate. The authentication algorithm
used to generate the AUTH payload is also included in the AUTH payload.
The peer node also includes the CERTREQ payload containing the list
of SHA-1 hash algorithms for local node authentication. For successful
server authentication, the CERTREQ payload must contain at least
one CA certificate that is in the trust chain of the peer certificate.
|
|
4.
|
Using the CA certificate
corresponding to the peer certificate, the local node first verifies that
the peer certificate in the CERT payload has not been modified and
the identity included in the IDi corresponds to the identity in
the peer certificate. If the verification is successful, using the
public key of the peer certificate, the local node generates the
expected AUTH payload and compares it with the received AUTH payload.
If they match, the authentication of the peer node is successful.
Otherwise, the local node sends an IKEv2 Notification message indicating
authentication failure.
|
|
5.
|
The local node responds
with the IKE_AUTH Response, including the IDr payload, setting
the CERT payload to the local node certificate, and including the
AUTH payload containing the signature of the IKE_SA_INIT
Response message (in step 2) generated using the private key of
the local node certificate. The authentication algorithm used to
generate the AUTH payload is also included in the AUTH payload.
|
|
6.
|
Using the CA certificate
corresponding to the local node certificate, the peer node first verifies
that the local node certificate in the CERT payload has not been
modified. If the verification is successful, using the public key
of the local node certificate, the peer generates the expected AUTH
payload and compares it with the received AUTH payload. If they
match, the local node authentication is successful. This completes
the IKE_AUTH exchange.
|
|
7.
|
An IPSec SA gets established
between the peer node and the local node. If more IPSec SAs are
needed, either the peer or local node can initiate the creation
of additional Child SAs using a CREATE_CHILD_SA
exchange.
|
Certificate Revocation Lists
Child SA Rekey Support
IKEv2 Keep-Alive Messages (Dead Peer Detection)
E-UTRAN/EPC Logical Network Interfaces Supporting IPSec Tunnels
| Interface | Description |
|---|---|
|
S1-MME Interface
|
This interface is the
reference point for the control plane protocol between the eNodeB
and the MME. S1-MME uses S1-AP (S1- Application Protocol) over SCTP (Stream
Control Transmission Protocol) as the transport layer protocol for
guaranteed delivery of signaling messages between the MME and the
eNodeB (S1).
The S1-AP over SCTP
signaling traffic gets carried over an IPSec tunnel.
When a subscriber UE
initiates a connection with the eNodeB, the eNodeB initiates an
IPSec tunnel with the MME, and SCTP signaling for all subsequent subscriber
UEs served by this MME gets carried over the same IPSec tunnel.
|
|
S1-U Interface
|
This interface is the
reference point for bearer channel tunneling between the eNodeB
and the S-GW.
Typically, the eNodeB
initiates an IPSec tunnel with the S-GW over this interface for
subscriber data traffic. But the S-GW may also initiate an IPSec
tunnel with the eNodeB if required.
|
|
S5 Interface
|
This interface is the
reference point for tunneling and management between the S-GW and
the P-GW.
Based on the requested
APN from a subscriber UE, the MME selects both the S-GW and the
P-GW that the S-GW connects to. GTP-C signaling traffic and GTP-U data
traffic are carried over the IPSec tunnel between the S-GW and P-GW
for the current and all subsequent subscriber UEs.
|
IPSec Tunnel Termination
Configuring Optional Features on the MME
Configuring X.509 Certificate-based Peer Authentication
IMPORTANT:
configure
certificate
name <cert_name>
pem data <cert_pem_data>
ca-certificate
name <ca_cert_name> pem
url <ca_cert_url>
end
configure
context <mme_context_name>
crypto
template <crypto_template_name>
ikev2-dynamic
certificate
name <cert_name>
ca-certificate
list ca-cert-name <ca_cert_name>
authentication
local certificate
authentication
remote certificate
end
Configuring Dynamic Node-to-Node IP Security on the S1-MME Interface
Creating and Configuring an IPSec Transform Set
configure
context <mme_context_name>
ipsec
transform-set <ipsec_transform-set_name>
encryption
aes-cbc-128
group
none
hmac
sha1-96
mode
tunnel
end
Creating and Configuring an IKEv2 Transform Set
configure
context <mme_context_name>
ikev2-ikesa
transform-set <ikev2_transform-set_name>
encryption
aes-cbc-128
group
2
hmac
sha1-96
lifetime <sec>
prf
sha1
end
Creating and Configuring a Crypto Template
configure
context <mme_context_name>
crypto
template <crypto_template_name>
ikev2-dynamic
authentication
local pre-shared-key key <text>
authentication
remote pre-shared-key key <text>
ikev2-ikesa
transform-set list <name1>
. . . <name6>
ikev2-ikesa
rekey
payload
<name>
match childsa match ipv4
ipsec
transform-set list <name1>
. . . <name4>
rekey
end
Binding the S1-MME IP Address to the Crypto Template
configure
context <mme_context_name>
mme-service <mme_svc_name>
bind
s1-mme ipv4-address <address>
ipv4-address <address> crypto-template <enodeb_crypto_template>
end
Configuring ACL-based Node-to-Node IP Security on the S1-MME Interface
Creating and Configuring a Crypto Access Control List
configure
context <mme_context_name>
ip
access-list <acl_name>
permit
tcp host <source_host_address>
host <dest_host_address>
end
Creating and Configuring an IPSec Transform Set
configure
context <mme_context_name>
ipsec
transform-set <ipsec_transform-set_name>
encryption
aes-cbc-128
group
none
hmac
sha1-96
mode
tunnel
end
Creating and Configuring an IKEv2 Transform Set
configure
context <mme_context_name>
ikev2-ikesa
transform-set <ikev2_transform-set_name>
encryption
aes-cbc-128
group
2
hmac
sha1-96
lifetime <sec>
prf
sha1
end
Creating and Configuring a Crypto Map
configure
context <mme_context_name>
crypto
map <crypto_map_name> ikev2-ipv4
match
address <acl_name>
peer <ipv4_address>
authentication
local pre-shared-key key <text>
authentication
remote pre-shared-key key <text>
payload
<name>
match ipv4
lifetime <seconds>
ipsec
transform-set list <name1>
. . . <name4>
exit
exit
interface
<s1-mme_intf_name>
ip
address <ipv4_address>
crypto
map <crypto_map_name>
exit
exit
port
ethernet <slot_number/port_number>
no
shutdown
bind
interface <s1-mme_intf_name> <mme_context_name>
end
Configuring Optional Features on the eGTP S-GW
Configuring X.509 Certificate-based Peer Authentication
IMPORTANT:
configure
certificate
name <cert_name>
pem data <cert_pem_data>
ca-certificate
name <ca_cert_name> pem
url <ca_cert_url>
end
configure
context <sgw_context_name>
crypto
template <crypto_template_name>
ikev2-dynamic
certificate
name <cert_name>
ca-certificate
list ca-cert-name <ca_cert_name>
authentication
local certificate
authentication
remote certificate
end
Configuring Dynamic Node-to-Node IP Security on the S1-U and S5 Interfaces
Creating and Configuring an IPSec Transform Set
configure
context <sgw_context_name>
ipsec
transform-set <ipsec_transform-set_name>
encryption
aes-cbc-128
group
none
hmac
sha1-96
mode
tunnel
end
Creating and Configuring an IKEv2 Transform Set
configure
context <sgw_context_name>
ikev2-ikesa
transform-set <ikev2_transform-set_name>
encryption
aes-cbc-128
group
2
hmac
sha1-96
lifetime <sec>
prf
sha1
end
Creating and Configuring a Crypto Template
configure
context <sgw_context_name>
crypto
template <crypto_template_name>
ikev2-dynamic
ikev2-ikesa
transform-set list <name1>
. . . <name6>
ikev2-ikesa
rekey
payload
<name>
match childsa match ipv4
ipsec
transform-set list <name1>
. . . <name4>
rekey
end
Binding the S1-U and S5 IP Addresses to the Crypto Template
configure
context <sgw_ingress_context_name>
gtpu-service <gtpu_ingress_service_name>
bind
ipv4-address <s1-u_interface_ip_address>
crypto-template <enodeb_crypto_template>
exit
egtp-service <egtp_ingress_service_name>
interface-type
interface-sgw-ingress
associate
gtpu-service <gtpu_ingress_service_name>
gtpc
bind address <s1u_interface_ip_address>
exit
exit
context <sgw_egress_context_name>
gtpu-service <gtpu_egress_service_name>
bind
ipv4-address <s5_interface_ip_address>
crypto-template <enodeb_crypto_template>
exit
egtp-service <egtp_egress_service_name>
interface-type
interface-sgw-egress
associate
gtpu-service <gtpu_egress_service_name>
gtpc
bind address <s5_interface_ip_address>
exit
exit
context <sgw_ingress_context_name>
sgw-service
<sgw_service_name>
-noconfirm
egtp-service
ingress service <egtp_ingress_service_name>
egtp-service
egress context <sgw_egress_context_name>
end
Configuring ACL-based Node-to-Node IP Security on the S1-U and S5 Interfaces
Creating and Configuring a Crypto Access Control List
configure
context <sgw_context_name>
ip
access-list <acl_name>
permit
tcp host <source_host_address>
host <dest_host_address>
end
Creating and Configuring an IPSec Transform Set
configure
context <sgw_context_name>
ipsec
transform-set <ipsec_transform-set_name>
encryption
aes-cbc-128
group
none
hmac
sha1-96
mode
tunnel
end
Creating and Configuring an IKEv2 Transform Set
configure
context <sgw_context_name>
ikev2-ikesa
transform-set <ikev2_transform-set_name>
encryption
aes-cbc-128
group
2
hmac
sha1-96
lifetime <sec>
prf
sha1
end
Creating and Configuring a Crypto Map
configure
context <sgw_ingress_context_name>
crypto
map <crypto_map_name> ikev2-ipv4
match
address <acl_name>
peer <ipv4_address>
authentication
local pre-shared-key key <text>
authentication
remote pre-shared-key key <text>
payload
<name>
match ipv4
lifetime <seconds>
ipsec
transform-set list <name1>
. . . <name4>
exit
exit
interface
<s1-u_intf_name>
ip
address <ipv4_address>
crypto
map <crypto_map_name>
exit
exit
port
ethernet <slot_number/port_number>
no
shutdown
bind
interface <s1_u_intf_name> <sgw_ingress_context_name>
end
configure
context <sgw_egress_context_name>
crypto
map <crypto_map_name> ikev2-ipv4
match
address <acl_name>
peer <ipv4_address>
authentication
local pre-shared-key key <text>
authentication
remote pre-shared-key key <text>
payload
<name>
match ipv4
lifetime <seconds>
ipsec
transform-set list <name1>
. . . <name4>
exit
exit
interface <s5_intf_name>
ip
address <ipv4_address>
crypto
map <crypto_map_name>
exit
exit
port
ethernet <slot_number/port_number>
no
shutdown
bind
interface <s5_intf_name> <sgw_egress_context_name>
end
Configuring Optional Features on the P-GW
Configuring X.509 Certificate-based Peer Authentication
IMPORTANT:
configure
certificate
name <cert_name>
pem data <cert_pem_data>
ca-certificate
name <ca_cert_name> pem
url <ca_cert_url>
end
configure
context <pgw_context_name>
crypto
template <crypto_template_name>
ikev2-dynamic
certificate
name <cert_name>
ca-certificate
list ca-cert-name <ca_cert_name>
authentication
local certificate
authentication
remote certificate
end
Configuring Dynamic Node-to-Node IP Security on the S5 Interface
Creating and Configuring an IPSec Transform Set
configure
context <pgw_context_name>
ipsec
transform-set <ipsec_transform-set_name>
encryption
aes-cbc-128
group
none
hmac
sha1-96
mode
tunnel
end
Creating and Configuring an IKEv2 Transform Set
configure
context <pgw_context_name>
ikev2-ikesa
transform-set <ikev2_transform-set_name>
encryption
aes-cbc-128
group
2
hmac
sha1-96
lifetime <sec>
prf
sha1
end
Creating and Configuring a Crypto Template
configure
context <pgw_context_name>
crypto
template <crypto_template_name>
ikev2-dynamic
ikev2-ikesa
transform-set list <name1>
. . . <name6>
ikev2-ikesa
rekey
payload
<name>
match childsa match ipv4
ipsec
transform-set list <name1>
. . . <name4>
rekey
end
Binding the S5 IP Address to the Crypto Template
configure
context <pgw_ingress_context_name>
gtpu-service <gtpu_ingress_service_name>
bind
ipv4-address <s5_interface_ip_address>
crypto-template <sgw_s5_crypto_template>
exit
egtp-service <egtp_ingress_service_name>
interface-type
interface-pgw-ingress
associate
gtpu-service <gtpu_ingress_service_name>
gtpc
bind ipv4-address <s5_interface_ip_address>
exit
pgw-service
<pgw_service_name>
-noconfirm
plmn
id mcc <id>
mnc <id>
primary
associate
egtp-service <egtp_ingress_service_name>
end
Configuring ACL-based Node-to-Node IP Security on the S5 Interface
Creating and Configuring a Crypto Access Control List
configure
context <pgw_context_name>
ip
access-list <acl_name>
permit
tcp host <source_host_address>
host <dest_host_address>
end
Creating and Configuring an IPSec Transform Set
configure
context <pgw_context_name>
ipsec
transform-set <ipsec_transform-set_name>
encryption
aes-cbc-128
group
none
hmac
sha1-96
mode
tunnel
end
Creating and Configuring an IKEv2 Transform Set
configure
context <pgw_context_name>
ikev2-ikesa
transform-set <ikev2_transform-set_name>
encryption
aes-cbc-128
group
2
hmac
sha1-96
lifetime <sec>
prf
sha1
end
Creating and Configuring a Crypto Map
configure
context <pgw_context_name>
crypto
map <crypto_map_name> ikev2-ipv4
match
address <acl_name>
peer <ipv4_address>
authentication
local pre-shared-key key <text>
authentication
remote pre-shared-key key <text>
payload
<name>
match ipv4
lifetime <seconds>
ipsec
transform-set list <name1>
. . . <name4>
exit
exit
interface <s5_intf_name>
ip
address <ipv4_address>
crypto
map <crypto_map_name>
exit
exit
port
ethernet <slot_number/port_number>
no
shutdown
bind
interface <s5_intf_name> <pgw_context_name>
end