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 (NR) DRX (Discontinuous Reception) Definition
    I. DRX (Discontinuous Reception) is a technology used in mobile communication designed to save battery power for user equipment (UE). Specifically, the mobile terminal (UE) and the network (RAN) negotiate so that the terminal's (UE) receiver only operates during data transmission and is switched off and enters a low-power state at other times.   II. DRX Framework: The 5G system supports the DRX architecture, allowing negotiation of idle mode DRX cycles between the UE and the AMF; the idle mode DRX cycle applies to: UEs in CM-IDLE state; UEs in CM-CONNECTED state that enter RRC Inactive state.   III. DRX Application: In 5G, if the UE wishes to use specific DRX parameters, it should include its preferred values during each initial registration and mobility registration process, respectively for NR/WB-EUTRA and NB-IoT; the registration and mobility registration processes performed on NB-IoT cells follow standard 5G procedures. For NB-IoT cells, the cell broadcasts an indication of support for UE-specific DRX for NB-IoT, and the UE can request UE-specific DRX for NB-IoT during the registration process regardless of whether the cell broadcasts this support indication. The AMF should determine the accepted DRX parameters based on the received UE-specific DRX parameters, and the AMF should accept the values requested by the UE, but the AMF may change the values ​​requested by the UE based on operator policy. The AMF should reply to the UE with the accepted DRX parameters for NR/WB-EUTRA and NB-IoT, respectively. ---- For detailed information on DRX parameters, please refer to TS 38.331 [28] and TS 36.331 [51].   Unless the UE has received the accepted DRX parameters for that RAT from the AMF, and for NB-IoT, the cell supports UE-specific DRX for NB-IoT; otherwise, the UE should apply the DRX cycle broadcast by the RAN in the cell. If the above parameters have been received, the UE shall apply the DRX cycle of the cell broadcast or the DRX parameters of the accepted RAT (as defined in TS 38.304 [50] and TS 36.304 [52]).   IV. The TAU and DRX periodic registration procedures do not change the UE's DRX settings. A terminal (UE) in CM-CONNECTED state and entering RRC Inactive mode will apply the DRX cycle negotiated with the AMF, the DRX cycle broadcast by the RAN, or the UE-specific DRX cycle configured by the RAN (as defined in TS 38.300 [27] and TS 38.304 [50]).

2025

12/26

Core Network 5G Terminal MM (Mobility Management) Capabilities
  MM (Mobility Management) is a key system in wireless networks for handling terminal (UE) mobility; in the 5G service-based architecture (SBA), it is handled by the AMF (Access and Mobility Management Function) unit to support ultra-high-speed, low-latency services; the 3GPP definition of 5GC handling of terminal (UE) mobility is as follows:   I. Core Network Capabilities In the 5G system, the core network capabilities of the terminal (UE) are divided into: S1 UE network capabilities (mainly used for E-UTRAN access-related core network parameters) and UE 5GMM core network capabilities (mainly including other UE capabilities related to 5GCN or EPS interworking); TS 24.501 [47] defines and includes non-radio-related capabilities (such as NAS security algorithms), where:   S1 UE network capabilities are transmitted between all CN nodes, including AMF to AMF, AMF to MME, MME to MME, and MME to AMF handovers. UE 5GMM core network capabilities are only transmitted during AMF to AMF handovers.   II. AMF and MM To ensure that the UE MM core network capability information stored in the AMF remains up-to-date, such as when the USIM is moved to another device when out of coverage, and the original device does not send a detach message, and in the case of cross-RAT registration area updates, the UE should send the UE MM core network capability information to the AMF via NAS messages during initial registration and mobility registration update processes. The AMF should always store the latest UE MM core network capability information received from the UE; when the UE provides UE MM core network capabilities through registration signaling, any UE MM core network capability information received by the AMF from the old AMF/MME will be replaced. If the UE's MM core network capability information changes (whether in CM-CONNECTED state or CM-IDLE state), the UE should perform a mobility registration update process the next time it returns to NG-RAN coverage (see clause 4.2.2 of TS 23.502 [3]).   III. MM Capabilities of 5G Terminals include: Attaching to EPC with request type "handover" in the PDN connection request message (see clause 5.3.2.1 of TS 23.401 [26]); EPC NAS; Sending SMS via NAS; LCS; 5G SRVCC from NG-RAN to UTRAN (as described in TS 23.216 [88]); Radio Capability Signalling Optimization (RACS); Network slice-specific authentication and authorization; Receiving WUS assistance information (E-UTRA) - see clause 5.4.9; Paging subgroup support indication (NR) - see clause 5.4.12; CAG - see clause 5.30.3.3; Subscription-based network slice simultaneous registration restriction - see clause 5.15.12; NSAG support - see clause 5.15.14; Minimizing Service Interruption (MINT) - clause 5.40.   IV. Multi-SIM Card Scenario: If a UE operates two or more USIMs and supports and intends to use one or more multi-USIM functions in a PLMN (see clause 5.38), the UE shall indicate its support for these one or more multi-USIM functions in the UE 5GMM core network capabilities for that USIM in that PLMN and include the following indications: Support for connection release; Support for voice service paging cause indication; Support for rejecting paging requests; Support for paging restriction;   Otherwise, a UE with multi-USIM capabilities but not intending to use them shall not indicate support for these one or more multi-USIM functions.

2025

12/25

5G Terminal Radio Capability Matching and Paging Assistance Information
  In 5G (NR) systems, due to the large amount of data in terminal (UE) radio capability information, only the basic content is usually transmitted to the relevant core network units during the access registration phase; when the core network queries other related functions of the terminal (such as VoNR support), it will match its radio (support) capabilities with the radio network (paging is required when the terminal is in idle state); the specific process is as follows:   I. Radio Capability Matching Request: If the AMF needs more information about UE radio capability support to set the IMS VoPS session support indication (see Section 5.16.3), the AMF can send a UE Radio Capability Matching Request message to the NG-RAN. This process is typically used during the registration process or when the AMF has not yet received the voice support matching indication (as part of the 5GMM context); where:   During the registration process, if the AMF has not yet obtained the UE's radio capabilities and if the RAT where the UE is located requires the establishment of an AN security context before retrieving radio capabilities, the AMF needs to provide a security context to the 5G-AN according to the "Initial Context Establishment" procedure defined in TS 38.413 [34] before sending the UE Radio Capability Matching Request message. ​ II.Paging Assistance Information is information related to the user equipment (UE) radio in the 5G system, used to assist the radio access network (RAN) in efficient paging. Paging assistance information includes:   2.1 UE Radio Capability Information: The UE radio capability information used for paging includes information derived from the UE radio capability information of the next-generation radio access network (NG-RAN) node (such as frequency band support information);   The AMF (Automatic Management Function) stores this information and needs to understand its content. Since the AMF only prompts the NG-RAN to retrieve and upload UE radio capability information (i.e., UE radio capability information) to the AMF in very few cases (e.g., during initial registration), and the AMF may be connected to multiple NG-RAN radio access technologies (RATs), the NG-RAN is responsible for ensuring that the UE radio capability information used for paging (derived by the NG-RAN node) includes all NG-RAN RAT information supported by the UE in that PLMN. To assist the NG-RAN in completing this task, the AMF, as described in TS 38.413 [34], provides its stored UE paging radio capability information in each NG-AP initial context setup request message sent to the NG-RAN. During AMF reselection, the terminal (UE) paging radio capability information is maintained in the core network and stored in the UCMF along with the radio capability information associated with the UE radio capability ID.   2.2 Paging Recommended Cell and RAN Node Information · Based on the information sent by the NG-RAN, the AMF uses this information when paging the UE to help determine which NG-RAN nodes to page and provides recommended cell information to each RAN node to optimize the paging success rate while minimizing the signaling load on the radio path. The RAN provides this information during N2 release.

2025

12/24