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!
Order of use of AMF interface protocols (authentication and call) in 5G
AMF (Access and Mobility Management Function) is a control plane (CU) functional unit in the 5G core network (CN). Radio network elements (gNodeBs) need to connect to AMF before they can access any 5G service. The connection between AMF and other units in the 5G system is shown in the figure below.     *Figure 1. Schematic diagram of AMF and 5G network element connection (solid lines in the figure represent physical connections, and dashed lines represent logical connections)   I. AMF Interface Functions N1[2]: The AMF obtains all connection and session-related information from the UE through the N1 interface. N2[3]: Communication between the AMF and the gNodeB related to the UE, as well as communication unrelated to the UE, is conducted through this interface. N8: All user and specific UE policy rules, session-related subscription data, user data, and any other information (such as data exposed to third-party applications) are stored in the UDM, and the AMF obtains this information through the N8 interface. N11[4]: The N11 interface represents the triggers for the AMF to add, modify, or delete PDU sessions on the user plane. N12: The AMF simulates an AUSF within the 5G core network and provides services to the AMF through the AUSF-based N12 interface. The 5G network represents a service-based interface, focusing on the AUSF and the AMF. N22: The AMF selects the best network function (NF) in the network using the NSSF. The NSSF provides network function location information to the AMF through the N22 interface. SBI[8]: The service-based interface is API-based communication between network functions.   II. AMF Application Protocols NAS[5]: In 5G, NAS (Non-Access Layer Protocol) is the control plane protocol on the radio interface (N1 interface) between the UE and AMF; it is responsible for managing mobility and session-related context within the 5GS (5G system). NGAP[6]: NGAP (Next Generation Application Protocol) is a control plane (CP) protocol used for signaling communication between the gNB and AMF. It is responsible for handling services related to the UE and services unrelated to the UE. SCTP[7]: Flow Control Transmission Protocol (SCTP) ensures the transmission of signaling messages between the AMF and the 5G-AN node (N2 interface). ITTI Messages[9]: Inter-task interface used to send messages between tasks.   III. Call Flow - UE Registration and Deregistration (Steps) The AMF first needs to register with the NRF to identify and communicate with the Network Function Location. When the UE powers on, it goes through a registration process. The AMF processes the registration and then receives the initial NAS UE message and registration request. This message is used to create an AMF identity for the UE. Then, the AMF checks the AMF the UE last registered with. If the old AMF address is successfully found, the new AMF will retrieve all UE contexts and initiate a deregistration procedure for the old AMF. The old AMF requests to release the SM context from the SMF and the UE context from the gNB.   IV. Terminal Authentication and Authorization If the new AMF does not detect any trace of the old AMF, it initiates the authorization and authentication process with the UE. It handles the identity verification process and requests an authentication vector from the AMF. It then sends an authentication request to the UE to set a security key and select a security algorithm for the channel, thereby ensuring secure data transmission. The AMF controls all NAS downlink/uplink transmission channels used for communication.

2025

11/07

What can Immediate MDT do for operators?
As mobile communication networks become increasingly complex, performance optimization and user experience improvement are crucial for operators. Previously, optimization engineers primarily relied on drive tests to perform (physical) measurements of the network to understand and control wireless coverage and performance. However, this testing method is costly, time-consuming, and not always comprehensive.   I. Minimum Drive Testing (MDT) is a wireless network measurement method designed by 3GPP for mobile communication networks. MDT allows the network to collect actual performance data directly from the User Equipment (UE) side, thereby reducing the need for manual drive testing. It is specifically divided into Logged MDT and Immediate MDT (iMDT).   II. Immediate MDT, as defined in 3GPP, refers to the real-time reporting of network performance data by the terminal equipment (UE) during a radio connection session. Unlike logged MDT, which stores data on the device for later upload, immediate MDT sends measurement results to the network, enabling operators to:   Identify network problems such as radio link failures (RLFs) in real time. Collect data at specific locations during the real-time session. Improve user performance in real time.   III. Key Points of Immediate MDT The Immediate MDT process during a connection session between the UE and the network mainly includes: MDT Configuration: The UE obtains the MDT configuration from the network. This configuration specifies which types of data need to be collected (e.g., RSRP, RSRQ, SINR, or call events). Measurement Timing: In a connected state, the UE periodically performs measurements based on specified conditions. Measurement parameters may include signal strength, quality metrics, and location data. Coverage Dead Zones and Radio Link Failures (RLF): If the UE finds itself in a coverage dead zone, an RLF may occur, prompting the MDT process to record signal strength and location for further analysis. Logger and RLF Indication: During an RLF event, the UE logs key information such as signal strength and location coordinates. After the RRC connection is re-established, an RLF log indication is created and sent. Re-establishment and Reporting: The UE needs to re-establish the RRC connection to reconnect. After the RRC reconnection, the UE sends the RLF log indication along with the recorded information. This helps the network identify the location and cause of the RLF, which is very useful for network optimization.

2025

11/06

5G(NR) RAN Learning -- PDU Session Resource Notification
I. PDU Session Resource Notification (PDU SESSION RESOURCE NOTIFY) is a 5G system notification to the core network element AMF that a QoS flow or PDU session established for a specific terminal (UE) has been released, is no longer being executed, or is being re-executed by an NG-RAN node controlled by a request notification. This procedure is also used to notify the NG-RAN node of QoS parameters that were not successfully accepted during the path handover request procedure. The entire procedure uses UE-related signaling.   II. PDU Session Resource Success Notification: As shown in Figure 8.2.4.2-1, the PDU session resource success operation is initiated by the GN-RAN node.     III. Key information for PDU session resource notification includes:   The NG-RAN node initiates this process by sending a PDU session resource notification message. The PDU SESSION RESOURCE NOTIFY message should contain information about PDU session resources or QoS flows that have been released, are no longer being executed, or have been re-executed by the NG-RAN node. For each PDU session where some QoS flows have been released, are no longer being executed, or have been re-executed by the NG-RAN node, a PDU session resource notification transport IE should be included, containing: A list of QoS flows released by the NG-RAN node (if any) in the QoS flow release list IE. If no other QoS flows are associated with the existing bearer after release (e.g., splitting the PDU session), the NG-RAN node and 5GC should consider the associated NG-U transport bearer to have been removed, and the associated NG-U UP TNL information to be available again. A list of GBR QoS flows that the NG-RAN node no longer executes or has re-executed by the NG-RAN node (if any) in the QoS flow notification list IE, along with the notification reason IE. For QoS flows indicated as no longer satisfied, the NG-RAN node may also indicate the alternative QoS parameter sets that can currently be satisfied in the Current QoS Parameter Set Index IE. For QoS flows indicated as no longer satisfied, the NG-RAN node may also indicate RAN feedback in the TSC Traffic Characteristics Feedback IE. A list (if any) of QoS flows whose QoS parameters have been updated but cannot be successfully accepted by the NG-RAN node during a path handover request should be included in the QoS Flow Feedback List IE, which may be associated with values ​​that can be provided. For each PDU session resource released by the NG-RAN node, a PDU session resource notification transmission released should be included in the "PDU Session Resource Notification Released Transmission IE" and the release reason should be included in the "Reason IE". If the User Plane Error Indication IE is set to "Received GTP-U Error Indication", the SMF (if supported) should consider the PDU session released due to receiving a GTP-U error indication through the NG-U tunnel, as described in TS 23.527. The NG-RAN node (if supported) should report the UE location information in the User Location Information IE in the PDU SESSION RESOURCE NOTIFY message. Upon receiving a PDU SESSION RESOURCE NOTIFY message, the AMF should transparently transmit a PDU Session Resource Notify Transfer IE or a PDU Session Resource Notify Released Transfer IE to the SMF associated with the relevant PDU session for each PDU session indicated in the PDU Session ID IE. Upon receiving the PDU Session Resource Notify Transfer IE, the SMF typically initiates the corresponding release or modification procedure on the core network side for PDU sessions or QoS flows that are identified as no longer satisfying. For each PDU session, if its PDU Session Resource Notification Transfer IE or PDU Session Resource Notification Released Transfer IE contains a Secondary RAT Usage Information IE, the SMF should process this information in accordance with TS 23.502. If the PDU Session Resource Notification message contains a User Location Information IE, the AMF should process this information in accordance with TS 23.501.

2025

11/05