logo
Send Message
Shenzhen Olax Technology CO.,Ltd
About Us
Your Professional & Reliable Partner.
Shenzhen OLAX Technology Co.,Ltd , which Located in Shenzhen, China. OLAX Technology established in 2010, It is a leading domestic supplier of wireless communication terminal technology solutions and equipment.Our main products are 4g C P E WIFI routers, USB WIFI dongles, modems. Pocket WIFI hotspot.G S M and C D M A fixed wireless telephones, terminals, Moreover, we support card lock, network lockand SIM card security.We have a core team with more than ten years of experience in R & D, sales ...
Learn More

0

Year Established:

0

Million+
Employees

0

Million+
customers served

0

Million+
Annual Sales:
China Shenzhen Olax Technology CO.,Ltd High quality
Trust Seal, Credit Check, RoSH and Supplier Capability Assessment. company has strictly quality control system and professional test lab.
China Shenzhen Olax Technology CO.,Ltd DEVELOPMENT
Internal professional design team and advanced machinery workshop. We can cooperate to develop the products you need.
China Shenzhen Olax Technology CO.,Ltd MANUFACTURING
Advanced automatic machines, strictly process control system. We can manufacture all the Electrical terminals beyond your demand.
China Shenzhen Olax Technology CO.,Ltd 100% SERVICE
Bulk and customized small packaging, FOB, CIF, DDU and DDP. Let us help you find the best solution for all your concerns.

quality Portable Wifi Routers & Wireless Wifi Routers manufacturer

Find Products That Better Meet Your Requirements.
Cases & News
The Latest Hot Spots
USIM in 5G (NR) system (1)
1.UE and UICC In the mobile communication system defined by 3GPP (3rd Generation Partnership Project), the user's terminal (UE) device is composed of: ME (mobile equipment) + UICC (Universal Integrated Circuit Card); where UICC is a Physical cards that are tamper-proof and resistant to software and hardware attacks. 2. UICC and USIM UICC can contain multiple applications, one of which is USIM; USIM securely stores and processes all sensitive data related to the user and home network. USIM is under the control of the home network operator; the operator selects the data to be configured in the USIM before issuance and remotely manages the USIM in the user's device through the OTA (over-the-air) mechanism. 3.USIM in 5G 3GPP defines USIM for the 5G system in Rel-15 for access and use in 3GPP and non-3GPP networks, allowing UE (user equipment) external data networks. USIM is defined in Rel-16 as network slice specific authentication. 4.First-time authentication is a mandatory procedure to allow UE (user equipment) to access 3GPP or non-3GPP networks. EAP-AKA' or 5G-AKA are the only authentication methods that allow primary authentication and the subscription credentials are always stored in the USIM when the terminal supports 3GPP access functionality. For primary authentication based on AKA, the mutual authentication performed in the USIM and the generation of the key material (integrity key IK and confidentiality key CK) sent by the USIM to the ME remain unchanged compared to 3G, 4G and Meets 3GPP TS 33.102 specification [3]. Changes in 5G Primary Authentication USIM include storing new security context and additional keying material in USIM (depending on the USIM's configuration). 4.1 5G support If the USIM supports storing 5G parameters, the ME will store the new 5G security context and the new keys defined for the 5G key hierarchy (i.e. KAUSF, KSEAF and KAMF) in the USIM. USIM can store a 5G security context for 3GPP access networks and a 5G security context for non-3GPP access networks. Storing the security context and key material in the USIM ensures faster reconnection when roaming (UICC moves from one ME to another). 4.2 NPN support Authentication in private networks (called independent non-public networks) can rely on the EAP framework supported by the 5G system; user equipment and service networks can support 5G AKA, EAP-AKA' or any other key generation EAP authentication method, where: ·When using AKA-based authentication methods, clause 6.1 of 3PPTS 33501[1] applies. ·When selecting an EAP authentication method other than EAP-AKA', the selected method determines the credentials required in the UE and network. How these credentials for EAP methods other than EAPAKA' are stored and processed within the UE is beyond the scope. But to ensure a high level of security for access to private networks, private network operators may decide to require the presence and use of a UICC containing USIM applications in order to securely store and process subscription credentials for EAP methods such as EAP-AKA' or EAP-TLS . 5. Secondary authentication This is an optional authentication based on EAP, conducted between UE (user equipment) and DN (external data network). Although the choice of EAP authentication method and credentials is beyond the scope of 3GPP, external data networks may decide to protect access to their DN by performing strong authentication thanks to the EAP-AKA' or EAP-TLS authentication method, UICC in the user device The presence of USIM on the DN securely stores and processes the credentials used to access the DN. Network Slice Specific Authentication Using network slice specific authentication between the user device and the AAA (Authentication, Authorization and Accounting) server to access the network slice is optional. Network slice specific authentication is based on the EAP framework and its user ID and credentials are different from the 3GPP subscription credentials. It follows the mandatory primary certification. Stakeholders deploying slices may decide to install USIM on the UICC of user devices to ensure a high level of security to access their slices and prevent the emergence of unauthorized users.
SIM Technology Innovation: An In-Depth Look at eSIM and vSIM
01.eSIM   eSIM, known as Embedded-SIM, or Embedded SIM, is a programmable, electronic SIM card technology whose main feature is that it does not require a physical slot, but rather an embedded chip that is integrated directly into the device's circuit board or inside other devices. Hardware part_     Integrated Circuit (IC) Chip: At the heart of the eSIM is a small IC chip that is built into the device's motherboard, similar to a physical SIM card. It contains the necessary hardware (CPU, ROM, RAM, EEPROM and serial communication unit) for storing and processing SIM data.   Software part_     Operating System (OS): The eSIM chip runs a dedicated operating system, often referred to as eUICC (Embedded Universal Integrated Circuit Card), which manages the SIM's functions, including data storage, secure processing and communication.     eSIM Production Process   ① Chip Manufacturing ② Chip testing ③ Integration into devices ④ Embedded software loading ⑤ Functional testing and verification   Virtual SIM (vSIM) is a SIM card technology without a physical form factor that allows devices to realize communication functions through software, including SoftSIM, CloudSIM, and others.   02.Virtual SIM (vSIM)   Virtual SIM (vSIM) is a SIM card technology without a physical form factor that allows devices to realize communication functions through software, including SoftSIM, CloudSIM, and others.   SoftSIM controls the information written to SoftSIM through the terminal provider, and the user purchases and uses communication services directly through the software without the intervention of the operator, which cuts off the direct connection between the user and the operator.   CloudSIM is a kind of SIM card function realized based on cloud computing technology, where users use network services on their devices through cloud services.   03.SIM service activation process   CloudSIM integrates the traffic resources of each operator into the cloud, selects operators according to the signal and network quality of different regions, and pushes them to the terminals to provide users with the best network services. The inclusion of multiple operators facilitates users to flexibly choose more favorable packages.       Do you want to learn more about SIM cards and other communication topics? We will continue to share more about this! See you in the next issue!
5G Core Network AMF Update Notification - Interface Message
In 5G (NR), AMF units do not need to be interrupted or restarted when making configuration changes or updates; they only need to notify the relevant network units. For mobile terminals (UEs) within their coverage area, the changes will be notified via the gNB in ​​the radio network, and the AMF will determine whether the UE needs to re-register with the AMF. The update definition process is as follows:   I. Configuration Update Process: As shown in Figure (1), the AMF determines whether the UE needs to reconfigure or register with the AMF based on the changes. That is, when the AMF detects a change in the configuration previously sent to the UE, it will initiate the configuration update process. In response to the UE's confirmation request, the AMF will send configuration update completion information to the AMF.   Figure 1. AMF Configuration Update Notification Flowchart   II. AMF Configuration Update Interface (Message)   [12] Construct Downlink RAN ​​Configuration Transmission [13] Send Downlink RAN ​​Configuration Transmission [12] Construct Downlink RAN ​​Status Transmission [13] Send Downlink RAN ​​Status Transmission [12] RAN Configuration Update Failed [13] Send RAN Configuration Update Failed [12] RAN Configuration Update Confirmation [13] Send RAN Configuration Update Confirmation [7] Construct Configuration Update Command [8] Send Configuration Update Command [12] Construct Downlink UE-Associated NRPPA Transmission [13] Send Downlink UE-Associated NRPPA Transmission [12] Construct Downlink Non-UE-Associated NRPPA Transmission [13] Send Downlink Non-E-Associated NRPPA Transmission [9] Configuration Update Complete [12] Construct AMF Configuration Update [13] Send AMF Configuration Update

2025

11/14

UE Authentication and Mobility Management AMF Interface Usage in 5G
The AMF unit plays a crucial role in the 5G core network; it is responsible for processing NAS messages transmitted transparently through the RAN (gNB) from the terminal (UE). The registration and authentication and mobility management of the terminal (UE) during initial access are completed by the AMF independently or jointly with other relevant network elements, as follows:   I. The order of AMF interface and message usage for 5G terminal authentication is shown in Figure (1); Figure 1. Message usage order of UE authentication AMF interface in 5G.     [11] UE authentication request [11] UE response [17] NRF discovery AUSF [25] Initialize SCP NF instance [11] NAMF Nausf authentication request [11] 5gAKA [11] Av5gAka contains authentication vector 5gAKA method [11] Amf_ue->SUCI [11] 5g AKA confirmation URL [11] SEAF starts authentication process [11] SUPI and Kseaf [11] Authentication successful [11] (or) Authentication failed   II. Mobility Management 5G networks provide high-speed and reliable connectivity for mobile users and devices, including vehicles, smartphones, and IoT devices. During mobility, the AMF is responsible for the transmission and processing of terminal-related information. Its interface (protocol) is used as follows; Figure 2. Order of AMF interface messages used when the UE moves in 5G   [5] Process registration request [5] UE sends initial NAS message to AMF [5] Set 5GS registration type: KSI, TSC [5] AMF new GUTI [5] Copy stream number, NR-TAI, NR-CGI from ran_ue [5] Check TAI[5] The algorithm selected by AMF should be the same as the NAS security algorithm [5] 5GMM request accepted [5] 5GMM processes registration update [5] 5GMM processes service request [6] The initial NAS service request message should contain security header type, ngKSI, TMSI and security header type [6] 5GMM processes service update[17] NRF discovers AUSF [25] Initialize SCP NF instance [5][6] AMF NAUSF authentication response, then confirm [5] Identity response SUCI[6] 5GMM status registered [13] NGAP handles path switching request [13] NGAP handles switching request [13] NGAP handles switching notification [13] NGAP handles Ran configuration update [5][6] 5GMM handles UL NAS transmission [5] 5GMM handles deregistration request [5] Set 5GS deregistration type [5] AMF sbi release all sessions [5] Clear paging information [5] Clear SM context [5] Unassociate NG with NAS  

2025

11/13

UPF Interface (Session Update and Deletion) Usage Order in 5G
  The UPF (User Plane Function) is one of the most important units in 5GC. It is a key unit that the Radio Network (RAN) interacts with during PDU data transmission. The UPF is also an evolution of CUPS (Control Plane and User Plane Separation), responsible for inspecting, routing, and forwarding packets within QoS flows in subscription policies. It uses SDF templates sent by the SMF through the N4 interface to enforce uplink (UL) and downlink (DL) traffic rules. When the service ends, it will allocate or terminate the QoS flow in the PDU session; the order of use of UPF interface session update and deletion is as follows; please refer to the order of use of UPF interface (protocol) and terminal call in 5G.   I. Session Modification Terminal-specific QoS flow is allocated through the PDU session modification process; additional dedicated QoS flow supports traffic with higher QoS requirements (such as voice, video, game traffic, etc.); the application of session modification (update) in UPF is shown in Figure (1); Figure 1. UPF interface usage order of terminal session modification (update) in 5G   [6] N4 processes session modification request [6] Remove existing PDR [6] Update PDR [6] Update FAR [6] Update URR [6] Update QER [6] Update BAR [6] Set up GTP node [6] Set up N3 TEID and QFI [6] [7] PFCP sends session modification response [5] N4 constructs session modification response [5] PFCP request accepted [5] PDR buffer initialized [5] PDR has been created [6] Send buffered data packets to gnB (if necessary) II. Session deletion When the terminal service session ends, QoS flow will be allocated or terminated in the PDU session. The session deletion usage order in the UPF interface is as follows: Figure 2.5G Terminal deletion UPF related interface usage order   [6] N4 processes session deletion request [6][7] PFCP sends session deletion request [5][1] Session URR usage status full report [1] Last report timestamp [1] Time trigger [1] Quota validity period report [1] Capacity trigger [1] Capacity quota report [5][1] UPF session URR snapshot (total bytes, total data packets, including uplink and downlink) [6][1] UPF session deletion [1] UPF session URR account all deletion: validity period deletion, quota time deletion, threshold time deletion. [13]PDR all deleted [13]FAR all deleted [13]URR all deleted [14]QER all deleted [13]BAR all deleted [13]From SEID

2025

11/12