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!
User data delivery in 5G (NR) in detail (2)
When a 5G user (UE) browses the Internet and downloads web content, the UP (user) side adds IP headers to the data and then hands it over to the UPF for processing, as described below;   I. UPF Processing   After adding the IP header, the user packets will be routed through the IP network to the UPF, which provides an entry point to the 5G core network. the IP network relies on its lower layers to transmit packets between routers; and the Ethernet operable Layer 2 agreement transmits IP packets between routers; The UPF is specifically responsible for mapping TCP/IP packets to specific QoS flows belonging to specific PDU sessions by using packet inspection to extract various header fields, which the UPF compares to a set of SDF (Service Data Flow) templates to identify the appropriate PDU sessions and QoS flows. For example, a unique combination of {source IP address 'X'; destination IP address 'Y'; source port number 'J'; destination port number 'K '} in unique combinations to map packets to specific PDU sessions and QoS flows; in addition, the UPF receives a set of SDF templates from the SMF (Session Management Function) during PDU session setup.   II.Data Forwarding   After identifying the appropriate PDU session and QoS flow, the UPF forwards the data to the gNode B using a GTP-U tunnel (the 5G core network architecture may link multiple UPFs - the first UPF must use a GTP-U tunnel to forward the data to another UPF, which then forwards it to the gNode B). Setting up a GTP-U tunnel for each PDU session implies that the TEID (tunnel endpoint identifier) within the GTP-U header identifies the PDU session but not the QoS flow. The “PDU Session Container” is added to the GTP-U header to provide information to identify the QoS flow. Figure 215 shows the structure of the GTP-U header containing the “PDU Session Container” as specified in 3GPP TS 29.281, and the content of the “PDU Session Container” as specified in 3GPP TS 38.415. III.PDU Session Container   As shown in Figure 216 below, when the value of “PDU Type” is “0”, it means that the PDU is a downlink packet instead of an uplink packet. the PPP (Paging Policy Presence) field indicates whether or not the header contains PPI (Paging Policy Indicator). (Paging Policy Indicator). the UPF may provide PPI to gNode B to provide paging priority that may be triggered by the arrival of a downlink packet - i.e. when the UE is in the RRC Inactive state. the RQI (Reflected QoS Indicator) specifies whether or not Reflected QoS should be applied to this QoS stream.     IV.GTP-U Tunneling   Using the UDP/IP protocol stack, UDP and IP headers are usually added before forwarding packets over the transport network.UDP provides simple connectionless data transfer.The structure of the UDP header is shown in Figure 217 below, where the source and destination ports identify the higher-level application. The higher-level application in this scenario is GTP-U whose registered port number is 2152.   V.GTP-U Headers   Adding IP headers for routing across GTP-U tunnels means that packets now have two IP headers. These are commonly referred to as the internal and external IP headers. Figure 218 shows these two headers; the UPF can use the DSCP field in the external IP header to prioritize packets, and the header associated with the GTP-U tunnel is removed at the far end of the tunnel, that is, at gNode B or, if the core network architecture is using chained UPF, at another UPF.

2024

09/30

User data transmission in 5G (NR) in detail
I. Network and Agreement Stack In SA (Independent Networking) 5G (NR) wireless network is usually divided into CU (Centralized Unit) and DU (Distributed Unit), where: DU (Distributed Unit) hosts the RLC, MAC, and PHY (Physical) layers, and CU (Centralised Unit) hosts the SDAP and PDCP layers; the user side of the network. The protocol stack is shown in the figure below:   II. the user data transfer to the end user (UE) to browse the Internet and download Web page content, for example, Internet browsers in the application layer using HTTP (Hypertext Transfer) protocol; assuming that the end user (UE) to host the Web page to be downloaded to the server to send the HTTP GET command, the application server will continue to use the TCP / IP (Transmission Control Protocol / Internet Protocol) packets to begin downloading the web content to the end user; the following header additions are required;   2.1 TCP Header Addition As shown in Figure 213, the TCP layer header is added with a standard header size of 20 bytes, but the size may be larger when optional header fields are included.The TCP header specifies the source and destination ports to identify higher-level applications. By default HTTP uses port number 80. the header also includes a sequence number to allow for reordering and packet loss detection at the receiver. The acknowledgement number provides a mechanism for acknowledging the packet, while the data offset defines the size of the header. The window size specifies the number of bytes the sender is willing to receive. Checksums allow for error bit detection in the header and payload. Emergency pointers can be used to indicate that certain data needs to be processed with high priority   2.2 IP Layer Header Addition Assuming IPv4 is used, the standard size of the header added at the IP layer, as shown in Figure 214, is 20 bytes (but the size may be larger when the optional header field is included).The IP header specifies the source IP address and the destination IP address, and the router uses the destination IP address to forward the packet in the appropriate direction. The version header field has a value of 4 when using IPv4, where the HDR (header) length field specifies the size of the header and the total length field specifies the size of the packet; DSCP (Differential Service Code Point) can be used to prioritize packets, and ECN (Explicit Congestion Notification) can be used to indicate network congestion. The agreement field specifies the type of content within the packet payload; TCP uses protocol number 6 for identification.  

2024

09/29

How are CM-Idle and CM-Connected 5G terminals different?
Whenever a terminal (UE) is ready to make a call or transmit data in a mobile communication system, it needs to connect with the core network first, which is due to the fact that the system temporarily removes the connection between the UR and the core network after the first time it is powered on or in an idle state for a period of time; the connection and management of the access connection between the terminal (UE) and the core network (5GC) in 5G (NR) is handled by the AMF unit, whose connection management (CM) is used to establish and release the control plane signaling connection between the UE and the AMF.   I. CM State Describes the signaling connection management (CM) state between the terminal (UE) and the AMF, which is mainly used for transmitting NAS signaling messages; for this purpose 3GPP defines two connection management states for the UE and the AMF respectively: CM-Idle (Connection Management in Idle state) CM-Connected (Connected state connection management)   CM-Idle and CM-Connected states are maintained by UE and AMF through NAS layer;   II.CM Characteristics Depending on the connection between the UE and the AMF. where: CM-Idle state the mobile equipment (UE) has not entered the signaling transmission state (RRC-Idle) with the core node (AMF). when the UE is in CM-Idle state it can move between different cells through mobile control according to the cell reselection principle. CM-Connected state the UE establishes a signaling connection (RRC-Connected and RRC-Inactive) with the AMF. the UE and the AMF can establish a connection based on the N1 (logical) interface will enter the CM-Connected state for the following intra interactions: RRC signaling between the UE and the gNB N2-AP signaling between the gNB and the AMF.   III.CM state transition The connected state of UE and AMF can be initiated by UE or AMF respectively, as shown in the following figure:   3.1 UE Initiated State Transition Once the RRC connection is established the UE state will enter CM-Connected; within the AMF once the established N2 context is received the UE state will enter CM-Connected; this can be performed by a registration request and a service request; where: When the UE is powered on for the first time, it selects the best gNB according to the cell selection process and sends a registration request to initiate the RRC connection setup signaling to the gNB and sends the N2 signaling to the AMF. The registration request triggers the transition from CM-Idle to CM-Connected. When the UE is in CM-Idle state and must send uplink data, the UE triggers a Service Request NAS message to the AMF and changes the CM-Idle to CM-Connected.   3.2 Network initiated state transition When there is downlink data to be transmitted to the CM-Idle UE, the network MUST use paging to initiate the state transition process. Paging triggers the UE to establish an RRC connection and send a Request NAS message to the AMF. The request triggers the N2 signaling connection to move the UE to CM-Connected.   When the signaling connection is released or the signaling connection fails, the UE can move from CM-Connected to CM-Idle.

2024

09/27