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 NSSF (Network Slice Selection Function)
    In the 5G system, the NSSF (Network Slice Selection Function) is a key component in the 5GC architecture, responsible for enabling and managing network slices. It provides two services: Nnssf_NSSelection (slice selection) and Nnssf_NSSAIAvailability (slice availability), which are defined as follows:   I. Network slicing allows operators to create multiple virtual networks on top of a shared physical infrastructure. Each slice can be customized according to specific service requirements, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), or massive machine-type communication (mMTC). The NSSF plays a core role in selecting the appropriate network slice for a given User Equipment (UE) and ensuring the correct resources are allocated.   II. The responsibilities of the NSSF, as defined in 3GPP TS 29.531, are: Selecting a set of network slice instances: Based on the UE's subscription, requested Network Slice Selection Assistance Information (NSSAI), and operator policies, the NSSF determines which slice instances should serve the UE. Determining allowed NSSAI and configured NSSAI mapping: Based on the UE's subscription (subscribed S-NSSAI from UDM), requested NSSAI, current service area (TA/PLMN), operator policies, and network constraints, the NSSF determines which S-NSSAI are available to the UE.   The specific tasks of the NSSF include: Calculating allowed NSSAI – selecting the set of S-NSSAI authorized for the UE in the current serving PLMN and registration area from the requested or subscribed list. Providing configured NSSAI mapping information – the NSSF returns the configured NSSAI mapping for the serving PLMN, which the AMF then passes to the UE via a registration accept message or UE configuration update message.   III.Roaming Scenarios: In this scenario, the NSSF provides S-NSSAI mapping between the VPLMN and HPLMN to ensure network slice compatibility and determine the AMF set – in some cases, the NSSF can also help determine the appropriate set of AMFs (Access and Mobility Management Functions) to serve the UE, especially when AMF reallocation is required.   IV. NSSF Services In 5GC, the NSSF provides services to AMF, SMF, NWDAF, and other NSSF instances in different PLMNs through a service-based interface (SBI) based on the Nnssf service. The main function of the NSSF is to provide network slice information to the AMF; the NSSF exposes two main services via SBI: Nnssf_NSSelection: Used by the AMF to retrieve network slice selection information. Nnssf_NSSAIAvailability: Used by the AMF to update the NSSF with information on the S-NSSAI supported within each tracking area (TA) and to subscribe to availability change notifications.

2026

02/06

QoS Flow in 5G – 3GPP R18 Definition
  I. QoS Model In 5G, the QoS Flow model supports two types of QoS flows: GBR QoS flows – QoS flows requiring guaranteed flow bit rate, and Non-GBR QoS flows – QoS flows that do not require guaranteed flow bit rate. The QoS model in 5G also supports Reflective QoS (see Reflective QoS - TS 23.501 Clause 5.7.5).   II.QoS and PDU In a 5G system, the QoS flow is the finest granularity for distinguishing QoS within a PDU session. The QoS Flow ID (QFI) is used to identify QoS flows in the 5G system. Within a PDU session: user plane traffic with the same QFI will receive the same traffic forwarding processing (e.g., scheduling, admission thresholds). The QFI resides in the N3 (and N9) encapsulation header, meaning no changes are required to the end-to-end packet header. All PDU call types should use the QFI. The QFI should be unique within a PDU session. QFI can be dynamically allocated or equal to 5QI (see Section 5.7.2.1).   III. QoS Control In 5GS, QoS flows are controlled by the SMF and can be pre-configured or established through the PDU session establishment process (see Section 4.3.2 of TS 23.502[3]) or the PDU session modification process (Section 4.3.3 of TS 23.502[3]).   IV.QoS Flow Characteristics 5G systems have the following characteristics: - A QoS profile provided by the SMF to the AN via the AMF through the N2 reference point, or pre-configured in the AN; - One or more QoS rules, and optional QoS flow-level QoS parameters (as described in TS 24.501[47]), which can be provided by the SMF to the UE via the AMF through the N1 reference point, and/or derived by the UE through application reflective QoS control; and - One or more UL and DL PDRs (SMF to UPF) provided by the SMF.   V. Default QoS Flow In 5GS, a PDU session needs to establish a QoS flow associated with a default QoS rule, and this QoS flow remains established throughout the entire lifecycle of the PDU session. This QoS flow should be a non-GBR QoS flow, and the QoS flow associated with the default QoS rule provides connectivity to the UE throughout the entire lifecycle of the PDU session.Furthermore, the QoS flow is associated with the QoS requirements specified by QoS parameters and QoS characteristics. Interoperability with EPS necessitates the recommendation that this QoS flow be of the non-GBR type.

2026

02/05

5G (NR) Network Analysis and Trigger Conditions
I. Network Analytics is a 5G system utilizing artificial intelligence/machine learning-driven real-time data analysis; it monitors and optimizes network performance, user experience, and resource allocation based on the 3GPP standardized NWDAF (Network Data Analytics Function). Network analytics achieves proactive closed-loop automation by collecting fine-grained data from the Radio Access Network (RAN), core network, and User Equipment (UE), thereby improving service quality, managing network slices, and predicting network behavior.   II. Network Analytics Features: Enabling network analytics provides mobile network operators with the following advantages: Increased Efficiency: Optimizing network resources and reducing total cost of ownership (TCO); User Experience Optimization: Monitoring and improving end-user quality of experience (QoE); Operations Optimization: Replacing passive manual troubleshooting with automated, proactive, and predictive operations; Vendor Interoperability: Using standardized interfaces to avoid vendor lock-in.   III. Key Network Analytics Nodes: NWDAF (Network Data Analytics Function): This is a core 5G function that collects data from multiple network nodes, generates and analyzes data, and provides insights to support automated operations. Fine-grained Real-time Data: Supports monitoring traffic at the user, session, and application levels to ensure high-quality service, especially for critical 5G services. Predictive and AI-driven: Utilizes machine learning to analyze historical and current data for proactive network management, such as predicting congestion or mobility issues. Automated Closed-loop: Enables the network to automatically adjust itself based on analytical insights without manual intervention. Network Slice Optimization: Provides specialized insights for managing the performance of different network slices, ensuring dedicated resources for specific services (e.g., high-bandwidth or ultra-low latency applications).   IV. Network Analytics Triggers: In the 5G system, the SMF requests or subscribes to analytical information from the NWDAF. The trigger conditions include the following conditions in the internal logic: - UE PDU session-related events subscribed to by other NFs (e.g., AMF, NEF); - UE access and mobility event reports from the AMF; - Locally detected events; - Received analytical information.   The trigger conditions may depend on the operator and SMF implementation strategy; when a trigger condition occurs, the SMF can decide whether any analytical information is needed; if needed, it requests or subscribes to analytical information from the NWDAF. When certain local events are detected, such as the number of PDU session establishments or releases within a specific area reaching a threshold, the SMF can request or subscribe to network analytics information related to "abnormal behavior" (as described in TS 23.288[86]) to detect any abnormal UE behavior within that area.

2026

02/04