Quality Portable Wifi Routers & Wireless Wifi Routers Manufacturer

  1.5G paging is based on operator configuration, and 5GS supports AMF and NG-RAN in applying different paging strategies for different types of traffic; specifically:   When the UE is in CM-IDLE state, the AMF performs paging and determines the paging strategy based on information such as local configuration, the NF that triggered the paging, and the information available in the request that triggered the paging. If NWDAF is deployed, the AMF can also use analytical data (i.e., statistical or predictive data - see TS 23.288 [86]) provided by NWDAF regarding UE mobility. When the UE is in CM-CONNECTED state and the RRC connection is in RRC_INACTIVE state, the NG-RAN performs paging and determines the paging strategy based on information such as local configuration and information received from the AMF (as described in TS 23.501 Section 5.4.6.3) and SMF (as described in TS 23.501 Section 5.4.3.2).   2.SMF Service Triggered Paging: For network-triggered service requests from the SMF, the SMF determines the 5QI and ARP based on the following information:   Downlink data packets (if the SMF performs buffering) or downlink data reports received from the UPF (if the UPF performs buffering). The SMF includes the 5QI and ARP corresponding to the QoS flow of the received downlink PDU in the request sent to the AMF. If the UE is in CM-IDLE state, the AMF can use, for example, the 5QI and ARP to derive different paging strategies, as described in Section 4.2.3.3 of TS 23.502 [3]. ----The AMF uses the 5QI to determine the appropriate paging strategy.   3.Paging Strategy Area: This is an optional function that allows the AMF to apply different paging strategies to different traffic or service types provided within the same PDU session, based on operator configuration. In the R18 version specifications, this function is only applicable to IP type PDU sessions, where, when 5GS supports Paging Policy Differentiation (PPD) functionality, the DSCP value (TOS in IPv4/TC in IPv6) is set by the application to indicate which paging policy the 5GS should apply to a specific IP packet, as described in TS23.228 [15]. The P-CSCF can support paging policy differentiation by marking packets related to specific IMS services (such as session voice defined in IMS multimedia telephony services) to be sent to the UE. ----This PPD function can be used to determine the paging cause indication for voice services, as described in Section 5.38.3 of TS23501. Operators should be able to configure the SMF to apply the paging policy differentiation function only to certain HPLMNs, DNNs, and 5QIs. For HR roaming, this configuration is done in the SMF in the VPLMN.   4.Roaming Paging: Paging Policy Differentiation (PPD) support in HR roaming requires inter-operator agreements, including the DSCP values associated with this function, where:   For network-triggered service requests and cases where the UPF caches downlink data packets, the UPF should include the TOS (IPv4)/TC (IPv6) value in the downlink data packet IP header and the corresponding QoS flow indication in the downlink data report sent to the SMF. When PPD is applicable, the SMF determines the Paging Policy Indicator (PPI) based on the DSCP value received from the UPF. For network-triggered service requests and cases where the SMF buffers downlink data packets, when PPD is applicable, the SMF determines the PPI based on the TOS (IPv4)/TC (IPv6) value in the received downlink data packet IP header and identifies the corresponding QoS flow from the QFI of the received downlink data packet. The SMF includes the PPI, ARP, and 5QI of the corresponding QoS flow in the N11 message sent to the AMF. If the UE is in CM-IDLE state, the AMF uses this information to generate a paging policy and sends a paging message to the NGRAN via N2.   Network configuration needs to ensure that the information used as a trigger for paging policy indication does not change during the 5GS period; the network configuration needs to ensure that the specific DSCP in the TOS (IPv4)/TC (IPv6) values ​​used as triggers for paging policy indication is correctly managed to avoid unintended use of certain paging policies; where: for a UE in RRC_INACTIVE state, the NG-RAN can enforce a specific paging policy in the case of NG-RAN paging, based on the 5QI, ARP, and PPI associated with the incoming downlink PDU. To achieve this, the SMF instructs the UPF to detect the DSCP in the TOS (IPv4)/TC (IPv6) value in the downlink PDU IP header (by using a downlink PDR containing the DSCP for that traffic) and transmit the corresponding PPI in the CN tunnel header (by using a QER containing the PPI value). The NG-RAN can then utilize the PPI in the CN tunnel header of the received downlink PDU to apply the corresponding paging policy for paging when the UE is in RRC_INACTIVE state.   ----In the case of home-routed roaming, the V-SMF is responsible for controlling the UPF settings for the PPI. In the case of a PDU session established with the I-SMF, the I-SMF is responsible for controlling the UPF settings for the PPI.   5.Paging Priority: This is a function that allows the AMF to include an indication in the paging message sent to the NG-RAN, indicating that the UE needs to be paged with priority. Whether the AMF includes paging priority in the paging message depends on the ARP value of the IP packet received from the SMF and waiting to be delivered in the UPF. If:   The ARP value is associated with a specific priority service (e.g., MPS, MCS), the AMF will include paging priority in the paging message. When the NG-RAN receives a paging message containing paging priority, it will prioritize the processing of that paging. When the AMF is waiting for a response from the UE to a paging message that does not include priority, if it receives another message from the SMF whose ARP value is associated with a specific priority service (e.g., MPS, MCS), the AMF will send another paging message containing paging priority to the (RAN). For subsequent messages, the AMF may decide, based on local policy, whether to send a paging message with a higher paging priority.   For UEs in the RRC Inactive state, the NG-RAN determines the paging priority based on the ARP associated with the QoS flow, configured according to the operator's policy, and core network-assisted RAN paging information from the AMF (as described in Section 5.4.6.3).

    In 5G networks, the network has two CM (Connection Management) connection states for terminals: CM-Idle and CM-CONNECTED. The CM-CONNECTED state is crucial for achieving seamless data flow and supports low-latency, large-scale IoT, and smart city applications. The reachability of the terminal (UE) in the CM-CONNECTED state is defined by 3GPP in TS 23.501 as follows:   I. Reachability in CM-CONNECTED state specifically includes: The AMF knows the UE's location at the serving (RAN) node granularity; When the UE becomes unreachable from the RAN's perspective, the NG-RAN notifies the AMF.   II. RRC Inactive State Terminal (UE): For terminals (UEs) in the RRC Inactive state, the radio access network (RAN) uses UE RAN reachability management (see TS 38.300 [27]). The location of the terminal (UE) in the RRC Inactive state is determined by the RAN at its (RAN) notification area granularity. Terminals (UEs) in the RRC Inactive state are paged in the cells of the RAN notification area assigned to that UE. The RAN notification area can be a subset of the cells configured in the UE's registration area, or all cells configured in the UE's registration area. A UE in the RRC Inactive state performs a RAN notification area update when it enters a cell that does not belong to the RAN notification area assigned to that UE.   Radio Access Network (RAN) Communication Area: In the 5G system, the RNA (Radio Access Network Notification Area) is a geographical area located within the 5GC registration area; this area consists of one or more cells belonging to one or more gNBs; where: When the UE transitions to the RRC Inactive state, the RAN configures a periodic RAN notification area update timer value for the UE, and the timer in the UE restarts with this initial timer value. After the periodic RAN notification area update timer in the UE expires, the UE in the RRC Inactive state performs a periodic RAN notification area update as specified in TS 38.300 [27].   To assist in UE reachability management in the AMF, the RAN uses a guard timer, whose value is longer than the RAN notification area update timer value provided to the UE. In the RAN, after the periodic RAN notification area update protection timer expires, the RAN should initiate the AN release procedure as specified in TS 23.502 [3]; the RAN may provide the AMF with the time elapsed since the RAN last contacted the UE.

  During the initial registration or mobility registration update process, the 5G terminal (UE) will initiate a connection with the network, which is the MICO (Mobile Initiated Connection Only) connection mode; where:   I. The MICO mode allows the AMF to determine whether to allow the UE to use MICO mode and indicate this to the UE during the registration process, based on local configuration, expected UE behavior and/or network configuration parameters (if available from the UDM), UE indicated preferences, UE subscription information, and network policies, or any combination thereof.   If NWDAF is deployed, the AMF may also use UE mobility and/or UE communication analysis data generated by NWDAF (see TS 23.288 [86]) to determine MICO mode parameters. If the UE does not indicate its preference for MICO mode during the registration process, the AMF should not activate MICO mode for that UE. II. The UE and AMF renegotiate the MICO mode during each subsequent registration process; when the UE is in the CM-CONNECTED state, the AMF can deactivate the MICO mode by triggering a mobility registration update process; this process is performed through the UE configuration update process as described in Section 4.2.4 of TS 23.502 [3]; where:   During the registration process, the AMF assigns a registration area to the UE. When the AMF indicates that the UE is in MICO mode, the registration area is not limited by the paging area size. If the AMF's service area covers the entire PLMN, the AMF may decide to provide the UE with a "full PLMN" registration area based on local policies and user information. In this case, re-registration due to mobility within the same PLMN is not applicable. If mobility restrictions are applied to a UE in MICO mode, the AMF needs to assign an allowed area/disallowed area to the UE as specified in Section 5.3.4.1. When the AMF indicates MICO mode to the UE, if the UE's CM state in the AMF is CM-IDLE, the AMF always considers the UE unreachable. For a UE in MICO mode and whose CM state in the AMF is CM-IDLE, the AMF will reject any downlink data transmission requests and provide the corresponding rejection reason. For NAS-based MT-SMS, the AMF will notify the SMSF that the UE is unreachable and then execute the mobile terminal SMS sending failure handling procedure described in TS 23.502 [3, Section 4.13.3.9]. III. Delayed Location Services: The AMF will enable delayed location services, allowing mobile terminal data or signaling communication only for UEs in MICO mode and only when they are in the CM-CONNECTED state.   IV. CM-IDLE State: UEs in CM-IDLE state do not need to listen for paging. UEs in MICO mode can stop any access layer procedures in the CM-IDLE state until the UE initiates a transition from CM-IDLE to CM-CONNECTED due to one of the following trigger conditions: The UE undergoes a change (e.g., configuration change) requiring an update of its registration information in the network. The periodic registration timer expires. MO signaling is pending (e.g., an SM procedure has been initiated). If the registration area assigned to a UE in MICO mode is not the "all PLMNs" registration area, the UE will determine whether it is within that registration area when it has MO data or MO signaling. If the UE is not within the registration area, before initiating MO data or MO signaling,   V. UE and Emergency Services: The UE will perform a mobility registration update; a UE initiating emergency services shall not indicate MICO preference during the registration process. When MICO mode is activated in the UE, the UE and AMF locally disable MICO mode after the successful completion of the emergency service PDU session establishment process. The UE and AMF shall not enable MICO mode until the AMF accepts the use of MICO mode during the next registration process. To enable emergency callback, the UE should wait for a UE implementation-specific duration after the emergency PDU session release before requesting the use of MICO mode.   VI. MT Mode: To achieve energy saving for mobile terminal (UE) MT reachability (e.g., for cellular IoT), enhancements to the MICO mode are specified in the following clauses: MICO mode with extended connection time; MICO mode with active time; MICO mode with periodic registration timer control.