Improvements in high priority plmn selection execution after deregistration procedure

Abstract

In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The method can be performed by a user equipment (UE). The UE identifies an occurrence of a logoff initiated by the UE. The UE determines whether the logoff is related to a timer that enables an N1 mode capability of the UE. In response to the logoff being related to the timer, the UE maintains the enabling of the N1 mode capability of the UE.

Description

[0001] Cross-references

[0002] This application claims priority to Indian Patent Application Serial No. 202421018264, entitled “Improvement to the Implementation of High-Priority PLMN Selection After Cancellation Process”, filed on March 13, 2024, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to communication systems, and more specifically, to techniques for handling the selection and execution of high-priority public land mobile networks (PLMNs) after the deregistration process. Background Technology

[0004] The statements in this section are provided only as background information in connection with this disclosure and may not constitute prior art.

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems can employ various multiple access technologies to support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. One example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband driven by the Third Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT), and other needs). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0007] The following is a simplified overview of one or more aspects to provide a basic understanding of them. This overview is not a comprehensive summary of all conceived aspects, nor is it intended to identify key or important elements of all aspects, nor does it limit the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description thereafter.

[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The method is executable by a user equipment (UE). The UE recognizes the occurrence of a deregistration initiated by the UE. The UE determines whether the deregistration is related to a timer that interferes with the activation of the UE's N1 mode capability. In response to the deregistration being related to the timer, the UE maintains the N1 mode capability enabled.

[0009] To achieve the foregoing and related objectives, one or more aspects include the features described in detail below and specifically pointed out in the claims. The following description and accompanying drawings illustrate certain exemplary features of one or more aspects. However, these features represent only a portion of the many ways in which the principles of the various aspects can be adopted, and this description is intended to cover all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a schematic diagram illustrating an example wireless communication system and access network.

[0011] Figure 2 This is a schematic diagram illustrating communication between a base station and a user equipment (UE) in an access network.

[0012] Figure 3 An example logical architecture for a distributed access network is shown.

[0013] Figure 4 An example physical architecture of a distributed access network is shown.

[0014] Figure 5 A schematic diagram of a time slot example centered on the downlink (DL).

[0015] Figure 6 A schematic diagram of a timeslot example centered on the uplink (UL).

[0016] Figure 7 A schematic diagram of a wireless communication system that supports the selection of a Public Land Mobile Network (PLMN) in a 5G network.

[0017] Figure 8 Flowchart of the method to be executed for high-priority PLMNs after the deregistration process. Detailed Implementation

[0018] The following detailed description, in conjunction with the accompanying drawings, is intended to describe various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details given to provide a thorough understanding of the various concepts. However, those skilled in the art will understand that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0019] Several aspects of a telecommunications system will now be introduced in conjunction with various devices and methods. These devices and methods will be described in detail below and illustrated by various modules, components, circuits, processes, algorithms, etc. (collectively referred to as "elements") shown in the accompanying drawings. These elements can be implemented by electronic hardware, computer software, or any combination of both. Whether these elements are implemented in hardware or software depends on the specific application and design constraints imposed on the overall system.

[0020] For example, a single element, any portion thereof, or any combination thereof may be implemented as a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described in this disclosure. One or more processors in the processing system can execute software. Software should be broadly understood as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or other names.

[0021] Therefore, in one or more example aspects, the described functionality can be implemented by hardware, software, or any combination of both. If implemented by software, these functions can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium accessible to a computer. For example, but not limited to, such computer-readable media can include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of instructions or data structures and is accessible to a computer.

[0022] Figure 1This diagram illustrates a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, user equipment (UE) 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0023] Base station 102 configured as 4G LTE (collectively referred to as the Evolved UMTS Terrestrial Radio Access Network, E-UTRAN) can interface with EPC 160 via backhaul link 132 (e.g., SI interface). Base station 102 configured as 5G NR (collectively referred to as the Next Generation RAN, NG-RAN) can interface with core network 190 via backhaul link 184. Among other functions, base station 102 may perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-access stratum (NAS) messages, NAS node selection, synchronization, Radio access network (RAN) sharing, Multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and alarm message delivery. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via backhaul link 134 (e.g., X2 interface). Backhaul link 134 may be wired or wireless.

[0024] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network containing small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include Home Evolved Node B (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. Communication link 120 may employ multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be implemented using one or more carriers. Base station 102 / UE 104 may use spectrum with a bandwidth of up to 7 MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) to allocate a total of Yx MHz (x component carriers) for transmission in each direction using carrier aggregation. Carriers may be adjacent or non-adjacent. Carrier allocation may be asymmetrical between DL and UL (e.g., DL may allocate more or fewer carriers than UL). Component carriers may include primary component carriers and one or more auxiliary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the auxiliary component carriers may be referred to as secondary cells (SCells).

[0025] Some UEs 104 can communicate with each other via device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication can be implemented through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0026] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with the Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0027] Cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, cell 102' can employ New Radio Access (NR) technology and use the same 5 GHz unlicensed spectrum as Wi-Fi access point 150. Employing NR in unlicensed spectrum can enhance the coverage and / or increase the capacity of the access network.

[0028] Base station 102, whether cell 102' or large area (e.g., macro base station), may include enhanced node B (eNB), gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, can communicate with UE 104 in the conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-millimeter wave frequencies. When gNB 180 operates at millimeter wave or near-millimeter wave frequencies, gNB 180 can be referred to as a millimeter wave base station. Extremely high frequency (EHF) belongs to the radio frequency (RF) portion of the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-millimeter waves can extend down to 3 GHz with wavelengths of 100 mm. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz, also known as centimeter waves. Communication using millimeter-wave / near-millimeter-wave radio frequency bands (e.g., 3 GHz - 300 GHz) suffers from extremely high path loss and short range. The millimeter-wave base station 180 can communicate with the UE 104 using beamforming 182 to compensate for the extremely high path loss and short range.

[0029] Base station 180 can transmit beamforming signals to UE 104 in one or more transmit directions 108a. UE 104 can receive beamforming signals from base station 180 in one or more receive directions 108b. UE 104 can also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 can receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 can perform beam training to determine their respective optimal receive and transmit directions. The transmit and receive directions of base station 180 can be the same or different. The transmit and receive directions of UE 104 can be the same or different.

[0030] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between the UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and BM-SC 170 are connected to the IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched Streaming Service (PS Streaming Service), and / or other IP services. BM-SC 170 can provide and deliver MBMS user services. BM-SC 170 can serve as an entry point for content provider MBMS delivery, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS delivery. MBMS gateway 168 can distribute MBMS traffic to base station 102 that belongs to a Multicast Broadcast Single Frequency Network (MBSFN) area and broadcasts specific services, and can be responsible for session management (start / stop) and collecting billing information related to enhanced MBMS (eMBMS).

[0031] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Location Management Function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with the Unified Data Management (UDM) 196. The AMF 192 is the control node that handles signaling between the UE 104 and the core network 190. Typically, the SMF 194 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 connects to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), packet-switched streaming services, and / or other IP services.

[0032] The base station may also be referred to as gNB, Node B, Evolved Node B (eNB), access point, base transceiver station, wireless base station, wireless transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or other suitable terms. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of these UE 104 devices may be referred to as Internet of Things (IoT) devices (e.g., parking meters, gas pumps, toasters, vehicles, heart rate monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or other suitable terms.

[0033] While this disclosure may relate to 5G New Radio (NR), it may also apply to other similar fields, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other radio / wireless access technologies.

[0034] Figure 2This is a block diagram of base station 210 communicating with user equipment (UE) 250 in the access network. In the downlink, IP packets from Evolved Packet Core (EPC) 160 can be provided to controller / processor 275. Controller / processor 275 implements Layer 3 and Layer 2 functions. Layer 3 includes the radio resource control (RRC) layer, and Layer 2 includes the packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, and medium access control (MAC) layer. The controller / processor 275 provides RRC layer functions related to system information (e.g., Master Information Block (MIB), System Information Blocks (SIBs)) broadcasting, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), mobility between radio access technologies (RATs), and measurement configuration for UE measurement reports; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to upper transport layer packet data units (PDUs), error correction via Automatic Repeat Request (ARQ), connection, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), and MAC transfer from TBs. SDU demultiplexing, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and MAC layer functions related to logical channel priority.

[0035] The transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical layer (PHY), may include error detection of the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and multiple-input multiple-output (MIMO) antenna processing. The TX processor 216 processes the mapping to the signal constellation according to various modulation schemes (e.g., Binary Phase-Shift Keying (BPSK), Quadrature Phase-Shift Keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). Encoded and modulated symbols can be split into parallel streams. Each stream can then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined via an inverse fast fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 274 can be used to determine coding and modulation schemes, as well as spatial processing. The channel estimates can be derived from the reference signal and / or channel state feedback transmitted by UE 250. Each spatial stream can then be provided to different antennas 220 via a separate transmitter 218TX. Each transmitter 218TX can be transmitted using a corresponding spatial stream modulated radio frequency carrier.

[0036] At UE 250, each receiver 254RX receives signals through its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the radio frequency carrier and provides this information to the receive (RX) processor 256. The TX processor 268 and RX processor 256 implement Layer 1 functions related to various signal processing functions. The RX processor 256 can perform spatial processing on the information to recover any spatial stream directed towards UE 250. If there are multiple spatial streams directed towards UE 250, the RX processor 256 can synthesize them into a single OFDM symbol stream. The RX processor 256 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 210. These soft decisions can be based on a channel estimate calculated by channel estimator 258. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 210 on the physical channel. The data and control signals are then provided to controller / processor 259, which implements Layer 3 and Layer 2 functions.

[0037] Controller / processor 259 may be associated with memory 260, which stores program code and data. Memory 260 may be referred to as computer-readable medium. In the uplink, controller / processor 259 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from EPC 160. Controller / processor 259 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0038] Similar to the functions described in conjunction with downlink transmission of base station 210, controller / processor 259 provides RRC layer functions related to system information (e.g., MIB, SIBs) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to upper transport layer PDUs, error correction via ARQ, RLC SDU connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority.

[0039] The channel estimate derived by channel estimator 258 based on a reference signal or feedback from base station 210 can be used by TX processor 268 to select appropriate coding and modulation schemes and facilitate spatial processing. The spatial stream generated by TX processor 268 can be provided to different antennas 252 via individual transmitters 254TX. Each transmitter 254TX can modulate an RF carrier with the corresponding spatial stream for transmission. Uplink transmission is processed at base station 210 in a manner similar to that described in conjunction with the receiver functionality of UE 250. Each receiver 218RX receives signals through its corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides this information to RX processor 270.

[0040] The controller / processor 275 may be associated with a memory 276 storing program code and data. This memory 276 may be referred to as a computer-readable medium. In the uplink, the controller / processor 275 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the user equipment (UE) 250. IP packets from the controller / processor 275 may be provided to the evolved packet core (EPC) 160. The controller / processor 275 is also responsible for error detection using acknowledgment (ACK) and / or negative acknowledgment (NACK) protocols to support Hybrid Automatic Repeat Request (HARQ) operation.

[0041] New radio (NR) can refer to a radio configured to operate based on a new air interface (e.g., an air interface based on Orthogonal Frequency Divisional Multiple Access (OFDMA)) or a fixed transport layer (e.g., non-Internet Protocol (IP)). NR can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in both uplink and downlink, and can include support for half-duplex operation using Time Division Duplexing (TDD). NR can include Enhanced Mobile Broadband (eMBB) services targeting wide bandwidth (e.g., above 80 MHz), millimeter wave (mmW) services targeting high carrier frequencies (e.g., 60 GHz), massive machine-type communications (mMTC) services targeting non-backward-compatible MTC technologies, and / or mission-critical services targeting ultra-reliable low-latency communication (URLLC).

[0042] It can support a single component carrier bandwidth of 100 MHz. In one example, an NR resource block (RB) can span 12 subcarriers with a subcarrier bandwidth of 60 kHz for 0.25 ms, or a bandwidth of 30 kHz for 0.5 ms (similarly, a 15 kHz subcarrier spacing provides a 50 MHz bandwidth over a 1 ms duration). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR slots) with a length of 10 ms. Each slot can indicate the link direction used for data transmission (i.e., downlink or uplink), and the link direction of each slot can be dynamically switched. Each slot can include downlink / uplink data and downlink / uplink control data. NR uplink and downlink slots can be combined as follows. Figure 5 and Figure 6 More detailed description.

[0043] The NR radio access network (RAN) may include a central unit (CU) and a distributed unit (DU). NR base stations (BS) (e.g., gNB, 5G Node B, Node B, Transmission Reception Point (TRP), Access Point (AP)) may correspond to one or more base stations. NR cells may be configured as access cells (ACells) or data-only cells (DCells). For example, the RAN (e.g., a central unit or a distributed unit) may configure the cell. A DCell may be a cell used for carrier aggregation or dual connectivity, but not for initial access, cell selection / reselection, or handover. In some cases, a DCell may not transmit a synchronization signal (SS); in others, it may. The NR base station may transmit downlink signals to the UE to indicate the cell type. Based on this cell type indication, the UE can communicate with the NR base station. For example, the UE can determine the NR base station for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0044] Figure 3 An example logical architecture of a distributed radio access network (RAN) 300 according to aspects of this disclosure is shown. A 5G access node 306 may include an access node controller (ANC) 302. This ANC may be the central unit (CU) of the distributed RAN. The backhaul interface to the Next Generation Core Network (NG-CN) 304 may terminate at this ANC. The backhaul interface to the adjacent Next Generation Access Node (NG-AN) 310 may terminate at this ANC. This ANC may include one or more TRPs 308 (also referred to as base stations, NR base stations, node Bs, 5G node Bs, access points, or other terms). As mentioned above, TRPs can be used interchangeably with "cells".

[0045] TRP 308 can be a distributed unit (DU). A TRP can connect to one ANC (ANC302) or multiple ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, a TRP can connect to multiple ANCs. A TRP can include one or more antenna ports. A TRP can be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0046] The local architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. This architecture can be defined as supporting fronthaul solutions across different deployment types. For example, the architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter). The architecture can share features and / or components with Long Term Evolution (LTE). Depending on various aspects, the Next Generation AN (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.

[0047] This architecture enables collaboration between and within TRPs 308. For example, collaboration can be pre-defined within a TRP and / or across TRPs via ANC 302. Depending on the circumstances, inter-TRP interfaces may not be required or may not exist.

[0048] Depending on various factors, the distributed RAN 300 architecture allows for dynamic configuration of segmentation logic functions. Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) protocols can be adaptively placed in the ANC or TRP.

[0049] Figure 4An example physical architecture of a distributed RAN 400 according to aspects of this disclosure is shown. A centralized core network unit (C-CU) 402 can carry core network functions. This C-CU can be centrally deployed. C-CU functions can be offloaded (e.g., to Advanced Wireless Service (AWS)) to handle peak capacity. A centralized RAN unit (C-RU) 404 can carry one or more ANC functions. Optionally, the C-RU can locally carry core network functions. The C-RU can be distributed. The C-RU can be located closer to the network edge. A distributed unit (DU) 406 can carry one or more TRPs. This DU can be located at the network edge with radio frequency (RF) capabilities.

[0050] Figure 5 This is a schematic diagram 500 illustrating an example of a downlink-centric (DL) timeslot. The downlink-centric timeslot may include a control section 502. The control section 502 may be present in the initial or beginning portion of the downlink-centric timeslot. The control section 502 may include various scheduling and / or control information corresponding to different portions of the downlink-centric timeslot. In some configurations, the control section 502 may be a physical downlink control channel (PDCCH), such as... Figure 5 As shown. The downlink-centric time slot may also include a downlink data portion 504. This downlink data portion 504 may sometimes be referred to as the payload of the downlink-centric time slot. The downlink data portion 504 may include communication resources used for communicating downlink data from a scheduling entity (e.g., a user equipment (UE) or a base station (BS)) to a subordinate entity (e.g., a UE). In some configurations, the downlink data portion 504 may be a physical downlink shared channel (PDSCH).

[0051] The downlink-centric timeslot may also include a common uplink portion 506. This common uplink portion 506 may sometimes be referred to as an uplink burst, common uplink burst, and / or other suitable terms. The common uplink portion 506 may include feedback information corresponding to other portions of the downlink-centric timeslot. For example, the common uplink portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include acknowledgment (ACK) signals, negative acknowledgment (NACK) signals, hybrid automatic repeat request (HARQ) indicators, and / or other suitable types of information. The common uplink portion 506 may include additional or alternative information, such as information related to random access channel (RACH) procedures, scheduling requests (SRs), and other suitable types of information.

[0052] like Figure 5 As shown, the end of the downlink data portion 504 can be temporally separated from the start of the common uplink portion 506. This temporal separation may sometimes be referred to as a gap, guard period, guard interval, and / or other various suitable terms. This separation provides time for the handover from downlink communication (e.g., a receiving operation by a dependent entity (e.g., a UE)) to uplink communication (e.g., a transmitting operation by a dependent entity (e.g., a UE)). Those skilled in the art will understand that the foregoing is merely one example of a downlink-centric time slot, and alternative structures with similar characteristics may exist without departing from the aspects described herein.

[0053] Figure 6 This is a schematic diagram 600 showing an example of an uplink-centric (UL-centric) timeslot. The uplink-centric timeslot may include a control section 602. The control section 602 may be present at the beginning or start of the uplink-centric timeslot. Figure 6 The control section 602 in the above-described combination can be similar to the above-described combination. Figure 5 The control portion 502 is described. The uplink-centric timeslot may also include an uplink data portion 604. This uplink data portion 604 may sometimes be referred to as the payload of the uplink-centric timeslot. The uplink portion may refer to the communication resources used for communicating uplink data from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 602 may be a Physical Downlink Control Channel (PDCCH).

[0054] like Figure 6As shown, the end of the control section 602 can be time-separated from the start of the uplink data section 604. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or other various suitable terms. This separation provides time for switching between downlink communication (e.g., a receiving operation by a scheduling entity) and uplink communication (e.g., a transmitting operation by a scheduling entity). The uplink-centric time slot may also include a common uplink section 606. Figure 6 The common uplink portion 606 in the above can be similar to the combination described above. Figure 5 The common uplink portion 506 is described. This common uplink portion 606 may also include, or alternatively include, information related to a channel quality indicator (CQI), a sounding reference signal (SRS), and various other suitable types of information. Those skilled in the art will understand that the foregoing is merely one example of an uplink-centric time slot, and alternative structures with similar characteristics may exist without departing from the aspects described herein.

[0055] In some cases, two or more dependent entities (e.g., UEs) can communicate with each other using sidelink signals. Practical applications of such sidelink communication can include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Everything (IoE) communication, Internet of Things (IoT) communication, mission-critical mesh networks, and / or various other suitable applications. Generally, a sidelink signal can refer to a signal that communicates from one dependent entity (e.g., UE1) to another dependent entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), although the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal can communicate using licensed spectrum (unlike wireless LANs that typically use unlicensed spectrum).

[0056] Figure 7 This is a schematic diagram 700 illustrating a wireless communication system supporting Public Land Mobile Network (PLMN) selection in a 5G network. In this example, a User Equipment (UE) 704 wirelessly communicates with a base station 702, which is connected to a first core network 710 supporting PLMN A. The first core network 710 includes an access and mobility management function (AMF) 714, and other components.

[0057] Similarly, the UE 704 communicates wirelessly with base station 722, which is connected to a second core network 720 supporting PLMN B. The second core network 720 includes AMF 724, as well as other components.

[0058] The UE 704 can perform PLMN selection to preferentially connect to a higher-priority PLMN. A timer (e.g., the periodic PLMN search timer T specified in the relevant 3GPP standard section, such as TS 23.122) can be configured to control the periodic search for available PLMNs. During the PLMN selection process, the UE 704 scans for available PLMNs and selects the highest-priority PLMN based on stored preferences or Steering of Roaming (SOR) information received during registration. The entire contents of TS 23.122, and the entire contents of any other 3GPP standards mentioned herein, are hereby incorporated by reference for all purposes.

[0059] For example, if UE 704 is camped on a visited PLMN (VPLMN), such as PLMN A, it will periodically use timer T to search for higher priority PLMNs, including Home Public Land Mobile Network (HPLMN) or Equivalent Home Public Land Mobile Network (EHPLMN). Upon detecting a higher priority PLMN (e.g., PLMN B), UE 704 initiates a deregistration procedure (e.g., deregistration procedure 734) to release the current session and switch to idle mode. Subsequently, UE 704 attempts to register on the higher priority PLMN B.

[0060] During the registration process (e.g., registration process 732), user equipment (UE) 704 sends a registration request to base station 702, which forwards the request to Access and Mobility Management Function (AMF) 714 in network 710. The registration request may include the UE's identity, capabilities, and selected Public Land Mobile Network (PLMN). AMF 714 performs authentication and establishes a security key with the UE 704. Upon successful authentication, AMF 714 sends a registration acceptance message to the UE 704 via base station 702. The registration acceptance message may include network configuration, permitted services, and optional roaming guidance (SOR) information for PLMN selection.

[0061] For example, when the UE 704 performs a registration process with the network 710, the network 710 includes SOR information in the registration acceptance message. This information, contained in the SOR container of the registration acceptance message, includes data such as the operator-controlled PLMN and the SOR timer.

[0062] SOR information can guide UE 704 in selecting a suitable PLMN during roaming. For example, when UE 704 registers with PLMN A, which uses an operator-controlled PLMN from its home PLMN (HPLMN), PLMN A provides SOR information to UE 704. UE 704 can then use the operator-controlled PLMN during the PLMN selection process.

[0063] If a UE supports 5G on a PLMN, and the PLMN operator has agreements with other operators regarding technologies such as 4G or 3G, then the network can instruct the UE to use a specific PLMN for 4G or other technologies. This is known as an operator-controlled PLMN.

[0064] The conditions under which the UE performs the deregistration procedure include the use of the SOR timer (e.g., the Tsor timer), as detailed in 3GPP specifications such as TS 23.122, particularly Annex C. These conditions specify when the UE should initiate the deregistration procedure.

[0065] The deregistration process (e.g., deregistration process 734) can be initiated by the UE 704 or the network 710 due to inactivity, higher priority PLMN detection, or network policy. If initiated by the UE 704, the UE sends a deregistration request to the base station 702, which forwards the request to the AMF 714. If initiated by the network 710, the AMF 714 sends a deregistration request to the UE 704 via the base station 702. The UE 704 sends a deregistration acceptance message to the AMF 714 via the base station 702 to confirm the deregistration. After the deregistration process is completed, all active Protocol Data Unit (PDU) sessions and services are released, and the UE 704 switches to idle mode.

[0066] Upon entering idle mode, UE 704 can attempt to obtain service on a higher-priority PLMN or a Standalone Non-Public Network (SNPN) by using timer T. Timer T controls the periodic search for service from a Home PLMN (HPLMN), an Equivalent Home PLMN (EHPLMN), or a higher-priority PLMN. UE 704 can then switch to connected mode.

[0067] In the SOR scenario, the UE's switch from idle mode to connected mode can be triggered under the following conditions: (1) the UE detects a higher priority PLMN and attempts to switch to the target PLMN; (2) the UE performs a periodic PLMN search based on timer T and detects a higher priority PLMN; or (3) the UE receives SOR information and decides to switch to a higher priority PLMN. In these scenarios, the UE establishes a Radio Resource Control (RRC) connection with the base station through a random access procedure and switches to connected mode for service transmission or PLMN handover.

[0068] The Roaming Orientation (SOR) timer (Tsor-cm) in connected mode is designed to prevent the UE from remaining in connected mode for an extended period. Specifically, this timer ensures that during roaming orientation in connected mode, the PDU session remains active only for a predetermined duration.

[0069] The Tsor-cm timer ensures that the UE does not maintain a PDU session for an excessively long time. The PDU session remains active only while the timer is running. When the timer stops or expires, the PDU session is released.

[0070] The UE can perform the deregistration process under the following conditions: (1) No PDU session or service is running the Tsor-cm timer; (2) The last running Tsor-cm timer is stopped due to the release of the relevant PDU session or other conditions (e.g., UE state transition); or (3) The Tsor-cm timer expires.

[0071] In addition, if the UE has a list of available PLMNs and determines that there is a PLMN with a higher priority than the currently selected VPLMN, or if the UE cannot determine whether there is a higher priority PLMN, the deregistration process can be performed.

[0072] The general procedures for the UE during the deregistration process are specified in the relevant sections of the 3GPP standard, such as Sections 4.4.3.3 and 4.9.3 of TS 23.502. During this process, the UE 704 behaves as if the timer T for periodically attempting to search for higher-priority networks has expired. This triggers the UE 704 to initiate a search for available PLMNs or SNPNs and attempt to register if a higher-priority network is detected.

[0073] The UE can be configured with N1 mode capability for 3GPP access, enabling it to communicate with the core network via an N1 reference point. The N1 reference point, such as N1 reference point 716, serves as the logical interface between the UE 704 and the AMF 714 for transmitting Non-Access Stratum (NAS) signaling. This N1 interface 716 supports direct signaling transmission for processes such as registration, deregistration, and PLMN selection. Although the N1 interface 716 is a logical entity, its physical transmission is implemented through the base station 702, which encapsulates NAS messages within Radio Resource Control (RRC) messages.

[0074] In operation, the UE 704 can perform a NAS procedure to communicate with the network 710 via reference point N1 716. In this context, messages transmitted from the network 710 to the UE 704 can be referred to as downlink (DL) NAS transmission messages, while messages transmitted from the UE 704 to the network 710 can be referred to as uplink (UL) NAS transmission messages.

[0075] For example, the UE 704 can include a PDU session establishment request in a 5G System Session Management (5GSM) message. This 5GSM message is encapsulated in a 5G System Mobility Management (5GMM) message and transmitted to the AMF 714 during NAS transmission at reference point N1 716.

[0076] If the UE 704 supports A / Gb mode or Iu mode, the N1 mode capability for 3GPP access should be disabled. This ensures compatibility with legacy network modes and prevents conflicts during network access.

[0077] Furthermore, a UE-initiated deregistration process can disable the UE's N1 mode capability. In this case, the disabling of the N1 mode capability is performed as part of the deregistration process, and if the N1 mode capability has already been disabled, the UE will not re-enable the N1 mode capability.

[0078] Conversely, if the disabling of the N1 mode capability for 3GPP access is not initiated by a deregistration process of a user equipment (UE) for 5GS service via 3GPP access (excluding cases caused by power-off), then UE 704 can choose to re-enable the N1 mode capability for the current Public Land Mobile Network (PLMN). This re-enablement process allows UE 704 to resume 5G service when appropriate conditions are met.

[0079] In the context of the deregistration process, specific provisions pertain to scenarios where a UE, in 5G connectivity mode, decides to obtain service on a higher-priority PLMN due to roaming guidance (SOR). The UE shall execute a UE-initiated deregistration procedure in accordance with the conditions specified in Annex C of TS 23.122.

[0080] However, potential problems may arise when the deregistration process is triggered by the UE. For example, when a UE-initiated deregistration process is triggered due to the expiration or termination of the Roaming Guided Orientation (SOR) timer (Tsor-cm) in connected mode, the UE will disable its 3GPP access N1 mode capabilities. Consequently, the UE cannot perform periodic PLMN searches, resulting in delays in the search for high-priority PLMNs.

[0081] To address potential issues, the UE can determine whether the UE-initiated deregistration process is related to a specific timer after deregistration occurs. For example, if the UE-initiated deregistration process is executed due to the expiration or termination of the Tsor-cm timer, which might interfere with the activation of N1 mode capabilities, the UE (e.g., UE 704) can re-enable the N1 mode capabilities for 3GPP access. Alternatively, in such scenarios, the UE can avoid disabling N1 mode capabilities. In other words, the UE can disable the disabling of N1 mode capabilities, thereby preventing N1 mode capabilities from being disabled.

[0082] In summary, when it is determined that the activation of N1 mode capability is interfered with by the Tsor-cm timer, the UE can maintain the activation of N1 mode capability. This ensures that even in scenarios where the Tsor-cm timer should disable N1 mode capability, the UE can still continue to support communication with the 5G core network (5GC) through the N1 interface.

[0083] Typically, during a UE-initiated deregistration process for 5GS services via 3GPP access, the N1 mode capability of 3GPP access is disabled. In the first configuration, when the UE-initiated deregistration process occurs, it is determined whether the deregistration is related to a timer that interferes with the activation of N1 mode capability. For example, it is determined whether the deregistration is triggered by the expiration or cessation of a Tsor-cm timer. If the deregistration is triggered by the expiration or cessation of a Tsor-cm timer, the UE can re-enable the N1 mode capability. For example, this re-enablement can occur during PLMN selection, Independent Non-Public Network (SNPN) selection, or SNPN selection for service bootstrapping via 3GPP access. Re-enabling the N1 mode capability ensures seamless service continuity during critical processes such as PLMN selection, SNPN selection, or service bootstrapping, thereby improving the user experience. The ability to re-enable the N1 mode capability during PLMN or SNPN selection also allows the UE to connect to the most suitable network, thereby improving network performance and reliability.

[0084] Alternatively, if the expiration or cessation of the Tsor-cm timer leads to deregistration, the UE can initially avoid disabling N1 mode capabilities. This method prevents the UE from disabling N1 mode capabilities in these specific circumstances. When deregistration is triggered by the expiration or cessation of the Tsor-cm timer, by preventing the disabling of N1 mode capabilities, the UE avoids unnecessary switching of N1 mode capabilities and saves the network resources required for subsequent re-enabling of N1 mode capabilities. This reduces signaling overhead and improves operational efficiency.

[0085] In this configuration, the UE determines whether deregistration is triggered by the Tsor-cm timer. This determination can be made after the deregistration process is complete. This configuration provides options for re-enabling or preventing the disabling of N1 mode capabilities.

[0086] In the second configuration, if the N1 mode capability for 3GPP access is disabled due to a deregistration procedure initiated by a UE for 3GPP access (or both 3GPP and non-3GPP access), and the UE is operating in single-registration mode (as specified in section 5.5.2.2.3 of TS 24.501), then the UE should re-enable the N1 mode capability for 3GPP access under the following conditions: (1) The UE attempts to obtain service on a higher priority PLMN or SNPN, as specified in Clause 4.4.3.3 of TS 23.122; and (2) The UE simulates the expiration of the timer T periodically due to the expiration or stop of the Tsor-cm timer.

[0087] In other words, if the N1 mode capability for 3GPP access is disabled due to a deregistration process initiated for a UE for 3GPP access or for both 3GPP and non-3GPP access, and the UE is operating in single-registration mode, when the UE attempts to obtain service on a higher priority PLMN or SNPN, the UE will re-enable the N1 mode capability for 3GPP access based on the expiration or termination of the Tsor-cm timer, simulating the expiration of the timer T.

[0088] Single registration mode refers to an operational mode in which the UE maintains a single registration context for both 3GPP and non-3GPP access types. In this mode, the UE registers with the 5G core network (5GC) through either 3GPP or non-3GPP access (but not both simultaneously). Single registration mode simplifies the registration management process by reducing the number of registration contexts maintained by the UE and the network, thereby minimizing signaling overhead and improving resource efficiency.

[0089] In the third configuration, if the UE supports A / Gb mode or Iu mode, but the deregistration process is initiated due to the expiration or termination of the Tsor-cm timer, the UE disables the N1 mode capability for 3GPP access. A / Gb mode refers to the operating mode where the UE connects to the core network via the GSM EDGE Radio Access Network (GERAN) using either the A or Gb interface, as defined in the 3GPP specifications. The A interface is used for circuit-switched (CS) services, and the Gb interface is used for packet-switched (PS) services. A / Gb mode enables the UE to support traditional GSM and GPRS / EDGE services. Iu mode refers to the operating mode where the UE connects to the core network via the UMTS Terrestrial Radio Access Network (UTRAN) using the Iu interface, as defined in the 3GPP specifications. The Iu interface supports both circuit-switched (CS) and packet-switched (PS) services, enabling the UE to operate in the UMTS network. Iu mode facilitates seamless integration with 3GPP-compliant networks and supports advanced services such as Voice over IP (VoIP) and high-speed data transmission.

[0090] In scenarios involving A / Gb or Iu modes, which are associated with legacy networks, disabling N1 mode capabilities prevents the UE from attempting to establish communication with the 5G core network while operating in a legacy network. This configuration saves resources and reduces power consumption.

[0091] However, if the deregistration is triggered by the expiration or termination of the Tsor-cm timer, it typically indicates that the UE may have temporarily lost network connectivity or entered an inactive state. In such cases, maintaining N1 mode capability ensures that the UE can promptly resume 5G service, thereby minimizing service interruption time. This configuration allows the UE to retain N1 mode capability for 5G networks while simultaneously supporting A / Gb mode or Iu mode. This capability is particularly critical for multi-mode UEs (capable of supporting 2G, 3G, 4G, and 5G networks) because it facilitates seamless switching between legacy and 5G networks without frequently enabling or disabling N1 mode capability.

[0092] In various configurations, when the activation of N1 mode capability is interfered with by the Tsor-cm timer, the UE can retain N1 mode capability to support efficient PLMN selection. This ensures that the UE continues to support communication with the 5G core network through the N1 interface, thereby achieving a simplified and uninterrupted PLMN selection process.

[0093] By maintaining N1 mode capabilities, the UE can avoid unnecessary service interruptions and ensure timely detection and selection of higher-priority PLMNs. This method enhances the UE's ability to prioritize network connectivity and optimize roaming behavior based on operator policies and user preferences.

[0094] Figure 8 A flowchart 800 describes a method for selecting and executing a high-priority PLMN after a deregistration process. This method can be executed by a UE (e.g., UE 704). In operation 802, the UE identifies the occurrence of a deregistration initiated by the UE. Subsequently, in operation 804, the UE determines whether the deregistration is related to a timer that interferes with the UE's N1 mode capability activation. Next, in operation 806, in response to the deregistration being related to the timer, the UE maintains the UE's N1 mode capability enabled.

[0095] In some configurations, maintaining the N1 mode capability of the UE may include disabling the N1 mode capability of the UE. In other configurations, maintaining the N1 mode capability of the UE may include re-enabling the N1 mode capability of the UE.

[0096] In some configurations, the timer may include a Steering of Roaming (SOR) timer (Tsor-cm) in connected mode. In some configurations, determining whether the deregistration is related to this timer may include determining whether the deregistration was triggered by the expiration or termination of the Tsor-cm. In some configurations, when the UE supports A / Gb mode or Iu mode and the deregistration is triggered by the expiration or termination of the Tsor-cm, the UE may disable the N1 mode capability for 3GPP access.

[0097] In some configurations, this deregistration can activate the selection of a Public Land Mobile Network (PLMN), a Standalone Non-Public Network (SNPN), or an SNPN used for service bootstrapping via 3GPP access.

[0098] In certain configurations, the N1 mode capability for 3GPP access can be enabled when a deregistration for 3GPP access or both 3GPP access and non-3GPP access triggers a disable of the N1 mode capability for 3GPP access, and the UE is operating in single registration mode, and when the UE attempts to obtain service on a higher priority Public Land Mobile Network (PLMN) or Independent Non-Public Network (SNPN).

[0099] In some configurations, this check can be performed after the logout is complete.

[0100] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is merely illustrative. Depending on design preferences, the specific order or hierarchy of blocks in the process / flowchart may be rearranged. Furthermore, some blocks may be combined or omitted. The appended method claims present the elements of each block in an illustrative order and are not intended to limit the scope to the specific order or hierarchy shown.

[0101] The foregoing description is intended to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily occur to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to limit them to the aspects shown herein, but should be given the full scope consistent with the language of the claims, wherein references to singular elements do not mean “only one”, unless otherwise stated, but rather “one or more.” The term “exemplary” as used herein means “as an example, instance, or illustration.” Any aspect described as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise expressly stated, the term “some” means one or more. Combinations such as “at least one A, B, or C,” “one or more A, B, or C,” “at least one A, B, and C,” “one or more A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one A, B, or C", "one or more A, B, or C", "at least one A, B, and C", "one or more A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, wherein any such combination may contain one or more members of A, B, or C. All known or hereafter known structural and functional equivalents of the elements of the various aspects described in this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, the contents disclosed herein, whether or not expressly recited in the claims, are not intended to be exclusive to the public domain. The terms "module", "mechanism", "element", "device", etc., should not be considered as substitutes for the term "apparatus". Therefore, unless an element is expressly stated as "apparatus for...", no claim element should be construed as an apparatus plus a functional clause.

Claims

1. A wireless communication method for a user equipment, comprising: Identify the occurrence of a logout initiated by the user equipment; Determine whether the deregistration is related to a timer that interferes with the N1 mode capability activation of the user equipment; as well as In response to the logout associated with the timer, the N1 mode capability of the user equipment is maintained.

2. The method of claim 1, wherein maintaining the N1 mode capability of the user equipment includes: Disable the disabling of the N1 mode capability for this user device.

3. The method of claim 1, wherein maintaining the N1 mode capability of the user equipment includes: Re-enable the N1 mode capability of this user device.

4. The method of claim 1, wherein the timer includes a roaming boot timer in connection mode.

5. The method of claim 4, wherein determining whether the cancellation is related to the timer includes: Determine whether the cancellation was triggered by the expiration or termination of the roaming boot timer.

6. The method of claim 5, wherein when the user equipment supports A / Gb mode or Iu mode and the deregistration is triggered by the expiration or cessation of the roaming boot timer, the user equipment disables the N1 mode capability of 3GPP access.

7. The method of claim 1, wherein the selection of the deregistration activation public terrestrial mobile network, the selection of an independent non-public network, or the selection of an independent non-public network for service bootstrapping via 3GPP access.

8. The method of claim 1, wherein when a deregistration for 3GPP access or for both 3GPP access and non-3GPP access triggers a disablement of the N1 mode capability for 3GPP access, and the user equipment is operating in single registration mode, and the user equipment enables the N1 mode capability for 3GPP access when the user equipment attempts to obtain service on a higher priority public terrestrial mobile network or an independent non-public network.

9. The method of claim 1, wherein the determination is performed after the cancellation is completed.

10. A device for wireless communication, the device being a user equipment, comprising: Memory; as well as At least one processor, coupled to the memory and configured as follows: Identify the occurrence of a logout initiated by the user equipment; Determine whether the deregistration is related to a timer that interferes with the N1 mode capability activation of the user equipment; as well as In response to the logout associated with the timer, the N1 mode capability of the user equipment is maintained.

11. The device of claim 10, wherein maintaining the N1 mode capability of the user equipment includes: Disable the disabling of the N1 mode capability for this user device.

12. The device of claim 10, wherein maintaining the N1 mode capability of the user equipment includes: Re-enable the N1 mode capability of this user device.

13. The device of claim 10, wherein the timer includes a roaming boot timer in connection mode.

14. The device of claim 13, wherein determining whether the cancellation is related to the timer includes: Determine whether the cancellation was triggered by the expiration or termination of the roaming boot timer.

15. The device of claim 14, wherein when the user equipment supports A / Gb mode or Iu mode and the deregistration is triggered by the expiration or cessation of the roaming boot timer, the user equipment disables the N1 mode capability of 3GPP access.

16. A computer-readable medium storing code for wireless communication of a user equipment, the medium storing computer-executable code, including methods for: Identify the occurrence of a logout initiated by the user equipment; Determine whether the deregistration is related to a timer that interferes with the N1 mode capability activation of the user equipment; and In response to the logout associated with the timer, the N1 mode capability of the user equipment is maintained.

17. The computer-readable medium of claim 16, wherein maintaining the user equipment's ability to enable the N1 mode comprises: Disable the disabling of the N1 mode capability for this user device.

18. The computer-readable medium of claim 16, wherein maintaining the N1 mode capability of the user equipment includes: Re-enable the N1 mode capability of this user device.

19. The computer-readable medium of claim 16, wherein the timer includes a roaming boot timer in a connected mode.

20. The computer-readable medium of claim 19, wherein determining whether the cancellation is related to the timer includes: Determine whether the cancellation was triggered by the expiration or termination of the roaming boot timer.

Images