Got it

LTE security

Created: Dec 1, 2020 07:31:19Latest reply: Dec 2, 2020 05:55:10 455 5 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello guys! can some tell me how 4G security work in network?

Regards,

Featured Answers
kunthea
Created Dec 2, 2020 05:55:10

Dear Friend!

The following are some of the principles of 3GPP E-UTRAN security based on 3GPP Release 8 specifications:

The keys used for NAS and AS protection shall be dependent on the algorithm with which they are used.
The eNB keys are cryptographically separated from the EPC keys used for NAS protection (making it impossible to use the eNB key to figure out an EPC key).
The AS (RRC and UP) and NAS keys are derived in the EPC/UE from key material that was generated by a NAS (EPC/UE) level AKA procedure (KASME) and identified with a key identifier (KSIASME).
The eNB key (KeNB) is sent from the EPC to the eNB when the UE is entering ECM-CONNECTED state (i.e. during RRC connection or S1 context setup).

thank you!
View more
  • x
  • convention:

Sokrin
Sokrin Created Dec 3, 2020 06:15:03 (0) (0)
helpful  

Recommended answer

BetterMing
Created Dec 1, 2020 07:47:39

Good day!


The procedure for establishing a connection between a UE and an eNodeB is as follows:


1. Identification. The UE sends an attach_request message to the MME through the eNodeB. The message contains the identity information and security capabilities of the UE, such as the IMSI.


2. Authentication. To verify the authenticity of the UE, the MME sends an authentication_request message to the UE after receiving an authentication request from the HSS. Then, the UE uses the master key to answer the request and sends an authentication_response message to the UE. If the authentication is successful, the UE and MME enter the security algorithm negotiation.


3. Security algorithm negotiation. The MEE selects an algorithm pair supported by the UE from the security capabilities in the attach_request message. Then, the MEE sends a security_mode_command message for integrity protection to the UE. In the UE, the MME replays the security capability of the UE. In this way, the security capability in the security_mode_command message is the same as that in the attach_request message sent by the UE. After verifying the message authentication code MAC in the security_mode_command message, the MME sends an encrypted and integrity-protected security_mode_complete message. The UE and MME establish a shared security environment, including the shared key for protecting the integrity and confidentiality of message exchange.


4. Secure temporary ID exchange. The MEE sends an attach_accept message for encryption and integrity protection to the UE. The attach_accept message contains a temporary ID (GUTI) for the UE. To prevent d*** of sensitive IMSI/IMEI information, the GUTI is used for communication between all UEs and the eNodeB/MME. The attach procedure is complete after the UE sends an attach_complete message. The UE and eNodeB generate a shared key for secure communication as a secure environment.

View more
  • x
  • convention:

Sokrin
Sokrin Created Dec 1, 2020 09:52:47 (0) (0)
Good to read  
All Answers
Hello, Sokrin.
It's nice to meet you in the community.
We're working on getting the right answer for you. Please rest assured that we'll be back with an answer shortly.
View more
  • x
  • convention:

Good day!


The procedure for establishing a connection between a UE and an eNodeB is as follows:


1. Identification. The UE sends an attach_request message to the MME through the eNodeB. The message contains the identity information and security capabilities of the UE, such as the IMSI.


2. Authentication. To verify the authenticity of the UE, the MME sends an authentication_request message to the UE after receiving an authentication request from the HSS. Then, the UE uses the master key to answer the request and sends an authentication_response message to the UE. If the authentication is successful, the UE and MME enter the security algorithm negotiation.


3. Security algorithm negotiation. The MEE selects an algorithm pair supported by the UE from the security capabilities in the attach_request message. Then, the MEE sends a security_mode_command message for integrity protection to the UE. In the UE, the MME replays the security capability of the UE. In this way, the security capability in the security_mode_command message is the same as that in the attach_request message sent by the UE. After verifying the message authentication code MAC in the security_mode_command message, the MME sends an encrypted and integrity-protected security_mode_complete message. The UE and MME establish a shared security environment, including the shared key for protecting the integrity and confidentiality of message exchange.


4. Secure temporary ID exchange. The MEE sends an attach_accept message for encryption and integrity protection to the UE. The attach_accept message contains a temporary ID (GUTI) for the UE. To prevent d*** of sensitive IMSI/IMEI information, the GUTI is used for communication between all UEs and the eNodeB/MME. The attach procedure is complete after the UE sends an attach_complete message. The UE and eNodeB generate a shared key for secure communication as a secure environment.

View more
  • x
  • convention:

Sokrin
Sokrin Created Dec 1, 2020 09:52:47 (0) (0)
Good to read  
Dear Friend!

The following are some of the principles of 3GPP E-UTRAN security based on 3GPP Release 8 specifications:

The keys used for NAS and AS protection shall be dependent on the algorithm with which they are used.
The eNB keys are cryptographically separated from the EPC keys used for NAS protection (making it impossible to use the eNB key to figure out an EPC key).
The AS (RRC and UP) and NAS keys are derived in the EPC/UE from key material that was generated by a NAS (EPC/UE) level AKA procedure (KASME) and identified with a key identifier (KSIASME).
The eNB key (KeNB) is sent from the EPC to the eNB when the UE is entering ECM-CONNECTED state (i.e. during RRC connection or S1 context setup).

thank you!
View more
  • x
  • convention:

Sokrin
Sokrin Created Dec 3, 2020 06:15:03 (0) (0)
helpful  

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.