Handling of network rejection or no response and equivalent PLMN or SNPN

Abstract

According to one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The method may be performed by a user equipment (UE). In some configurations, the UE maintains a single equivalent network list for a first network. The UE performs a registration procedure or a deregistration procedure on the first network over the first access, where the user equipment is being registered over a second access of the first network, or the user equipment has been registered over the second access of the first network. In the registration process or the deregistration process, the UE maintains the single equivalent network list in response to an event in the registration process or the deregistration process. The event may include receiving a cause # 13 in a Downlink Non-Access Stratum (NAS) message over the first access, where the cause indicates that roaming is not allowed in the tracking area, or encountering a registration attempt counter equal to 5.

Description

[0001] Cross-referencing This application claims priority to Indian Provisional Application No. 202321065267, filed on September 28, 2023, entitled “NETWORKREJECTION OR NO RESPONSE AND HANDLING OF EQUIVALENT PLMN OR SNPN”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0002] This disclosure generally relates to communication systems, and more specifically, to techniques for methods and apparatuses for performing network denial or no response and processing equivalent public land mobile networks (PLMNs) or independent non-public networks (SNPNs). Background Technology

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

[0004] 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 may employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of these multiple access technologies include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

[0005] These multiple access technologies are applicable to various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released through the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT), and others). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology still requires further improvement. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of them. This overview is not a comprehensive overview of all anticipated aspects and is neither intended to identify key or essential elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present certain concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, a computer-readable medium, and apparatus thereof are provided. The method can be performed by a user equipment (UE). In some configurations, the UE maintains a single list of equivalent networks for a first network. The UE performs a registration or deregistration process through a first access of the first network, wherein the user equipment is registering to a second access of the first network, or the user equipment has already registered to the second access of the first network. During the registration or deregistration process, the UE maintains the single list of equivalent networks in response to events occurring during the registration or deregistration process.

[0008] To achieve the foregoing and related objectives, one or more aspects include the following features, which are fully described and specifically pointed out in the claims. The following description and drawings detail certain illustrative features of one or more aspects. However, these features illustrate only a portion of several ways in which the principles of the various aspects may be adopted, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

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

[0010] Figure 2This is a block diagram showing a base station communicating with the UE in the access network.

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

[0012] Figure 4 An example physical architecture for a distributed radio access network is shown.

[0013] Figure 5 This is a schematic diagram illustrating an example of a time slot centered on DL.

[0014] Figure 6 This is a schematic diagram illustrating an example of a time slot centered on UL.

[0015] Figure 7 This is a schematic diagram illustrating an example process of a UE registering to the first access point of a first network.

[0016] Figure 8 This is a schematic diagram illustrating an example process by which a UE performs mobility and periodic updates to a first access point of a first network.

[0017] Figure 9 This is a schematic diagram illustrating an example process of a UE performing a deregistration process in the first access of a first network.

[0018] Figure 10 This is a schematic diagram illustrating an example process between the UE and two access points of the first network.

[0019] Figure 11 This is a flowchart illustrating an example process of a UE registering to two access points on the same network.

[0020] Figure 12 This is a flowchart illustrating an example process of a UE registering to two different networks.

[0021] Figure 13 This is a flowchart of the UE wireless communication method (process). Detailed Implementation

[0022] The embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configuration in which the concepts described herein can be practiced. Specific details are included to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some examples, known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0023] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in the embodiments described below, and will be illustrated in the accompanying drawings by various blocks, components, circuits, processes, and algorithms (collectively referred to as “elements” below). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented in hardware or software depends on the specific application and design constraints imposed on the overall system.

[0024] Components, any part of components, or any combination of components can be implemented as an example of a "processing system" including 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 circuits, and other suitable hardware configured to perform the various functions described throughout this invention. One or more processors in the processing system can execute software. Whether referred to as software, firmware, intermediate software, microcode, hardware description language, or something else, software should be broadly interpreted 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, processes, and functions.

[0025] Therefore, in one or more aspects, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored on 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 by a computer. Examples, 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, and combinations of the above computer-readable media types, or any other medium for storing computer-executable code in the form of computer-accessible instructions or data structures.

[0026] Figure 1 This is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user interface unit (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0027] Base station 102 configured for 4G (collectively referred to as the Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network, E-UTRAN) is connected to the core network interface 160 via backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN, NG-RAN) is connected to the core network interface 190 via backhaul link 184. In addition to 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 transmission. Base station 102 may communicate directly or indirectly (e.g., via EPC 160 or core network 190) with each other via backhaul link 134 (e.g., X2 interface). Backhaul link 134 may be wired or wireless.

[0028] Base station 102 can wirelessly communicate with UE 104. Each of base stations 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 that includes both small cells and macro cells can be called a heterogeneous network. A heterogeneous network may also include home-evolved node B (HeNB), where HeNB can provide services to restricted groups called closed subscriber groups (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) transmission (also called reverse link) from UE 104 to base station 102 and / or downlink (DL) transmission (also called forward link) transmission from base station 102 to UE 104. Communication link 120 may use Multiple-Input And Multiple-Output (MIMO) antenna technology, which includes spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use a spectrum of up to 7 MHz bandwidth per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.), where each carrier is allocated in a total of up to Yx MHz of carrier aggregation (x component carriers) for transmission in each direction. Carriers may be adjacent to each other or not. The allocation of carriers for DL ​​and UL may be asymmetrical (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0029] Some UEs 104 can communicate with each other using device-to-device (D2D) communication links 158. D2D communication links 158 can use DL / UL WWAN spectrum. D2D communication links 158 can use one or more sidelink channels, such as the 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 conducted through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0030] The wireless communication system may further include a Wi-Fi access point (AP) 150, wherein the Wi-Fi AP 150 communicates with a 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.

[0031] Cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as Wi-Fi AP 150. Employing NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

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

[0033] Base station 180 can transmit beamformed signals to UE 104 in one or more transmit directions 108a. UE 104 can receive beamformed signals from base station 180 in one or more receive directions 108b. Base station 106 can perform beamformed signal transmission with UE 104 in one or more beam directions (108c, 108c'). UE 104 can also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 can receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 can perform beamforming to determine the optimal receive and transmit directions for each base station 180 / UE 104. 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.

[0034] EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an 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 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-switching streaming service (PSS), and / or other IP services. BM-SC 170 can provide functions for MBMS user service provision and delivery. BM-SC 170 can serve as an entry point for MBMS transmission by content providers, can be used to authorize and initiate MBMS bearer services in public land mobile networks (PLMNs), and can be used to schedule MBMS transmissions. MBMS gateway 168 can be used to allocate MBMS services to base stations 102 that belong to broadcast-specific services in multicast broadcast single-frequency network (MBSFN) areas, and can be responsible for session management (start / stop) and collection of payment information related to evolved MBMS (eMBMS).

[0035] 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 can 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 streaming and session management. All user Internet Protocol (IP) data 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, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0036] A base station may also be referred to as a gNB, Node B (NB), eNB, AP, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit and receive point (TRP), or other suitable terms. Base station 102 provides UE 104 with access to EPC 160 and core network 190. Examples of UE 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, automobiles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UE 104 devices may also be referred to as IoT devices (e.g., parking timers, air pumps, ovens, cars, heart monitors, etc.). UE 104 may also be referred to as 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, mobile phone, user agent, mobile user, user, or other suitable terms.

[0037] Although this invention may refer to 5G New Radio (NR), the present invention is applicable to other similar fields, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM) or other wireless / radio access technologies.

[0038] Figure 2This is a block diagram illustrating communication between base station 210 and UE 250 in the access network. In the DL, IP packets from core network 160 or core network 190 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, PDCP layer functions, RLC layer functions, and MAC layer functions. The RRC layer functions are associated with system information (e.g., MIB, SIB) broadcasting, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting. The PDCP layer functions are associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions. The RLC layer functions are associated with the transmission of upper-layer protocol data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs. The MAC layer functions are associated with mapping between logical channels and transport channels, and MAC on transport blocks (TBs). This is associated with SDU multiplexing, demultiplexing of MAC SDUs from TB, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority ordering.

[0039] The transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding on the transport channel, interleaving, rate matching, mapping on the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 216 processes the mapping to the signal constellation based on 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)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 274 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate can be derived from the reference signal transmitted by UE 250 and / or channel state feedback. Each spatial stream can then be provided to different antennas 220 via transmitters 218TX in respective transmitters and receivers 218. Each transmitter 218TX can modulate an RF carrier using the corresponding spatial stream for transmission.

[0040] In UE 250, each receiver 254RX (transceiver 254 includes receiver 254RX and transmitter 254TX) receives signals through a corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 256. The TX processor 268 and RX processor 256 implement Layer 1 functions associated with various signal processing functions. The RX processor 256 performs spatial processing on the information to recover any spatial streams destined for UE 250. If multiple spatial streams are destined for UE 250, they can be combined into a single OFDM symbol stream by the RX processor 256. The RX processor 256 then uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes individual OFDM symbol streams 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. Soft decision is based on the channel estimate calculated by channel estimator 258. The aforementioned soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 210 on the physical channel. These data and control signals are then provided to controller / processor 259, which implements Layer 3 and Layer 2 functions.

[0041] 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 UL, controller / processor 259 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transmission and logical channels to recover IP packets from EPC 160 or core network 190. Controller / processor 259 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0042] Similar to the functional description related to DL transmission of base station 210, controller / processor 259 provides RRC layer functions, PDCP layer functions, RLC layer functions, and MAC layer functions. The RRC layer functions are associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting. The PDCP layer functions are associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification). The RLC layer functions are associated with the transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs. The MAC layer functions are associated with mapping between logical channels and transport channels, MAC SDU multiplexing on TB, demultiplexing of MAC SDUs from TB, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority ordering.

[0043] The TX processor 268 can use the channel estimate derived from the reference signal transmitted by the channel estimator 258 or from the feedback to select a suitable coding and modulation scheme, and facilitate spatial processing. The spatial stream generated by the TX processor 268 can be provided to different antennas 252 via each transmitter 254TX. Each transmitter 254TX can use the corresponding spatial stream to modulate the RF carrier for transmission. Processing UL transmissions in the base station 210 is similar to the function of the receiver in the UE 250 to which it is connected. Receiver 218RX in each transmitter and receiver 218 receives signals through a corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 270.

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

[0045] NR refers to a radio configured to operate under a new air interface (e.g., in addition to OFDMA-based air interfaces) or a fixed transport layer (e.g., in addition to IP). NR can use OFDM with a cyclic prefix (CP) in both UL and DL, and can include support for half-duplex operation using Time Division Duplexing (TDD). NR can include tasks for enhanced mobile broadband (eMBB) services with wide bandwidths (e.g., exceeding 80 MHz), millimeter wave (mmW) services with high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) services for non-backward-compatible machine-type communication (MTC) technologies, and / or services for ultra-reliable low-latency communication (URLLC).

[0046] It can support a single-component carrier bandwidth of 100MHz. In one example, the NR RB can span 12 subcarriers, with a subcarrier bandwidth of 60kHz over a duration of 0.25 milliseconds or 30kHz over a duration of 0.5 milliseconds (similarly, a 50MHz BW for a 15kHz SCS over a duration of 1 millisecond). Each radio frame can include 10 subframes (10, 20, 40, or 80 NR slots) with a length of 10 milliseconds. Each slot can indicate the link direction for data transmission (e.g., DL or UL), and the link direction of each slot can be dynamically switched. Each slot can include DL / UL data and DL / UL control data. (About...) Figure 5 and Figure 6 The UL and DL time slots used for NR can be described in more detail below.

[0047] NR RAN can include a central unit (CU) and distributed units (DU). NR base stations (e.g., gNB, 5G Node B, Node B, Transmission Reception Point (TRP), AP) can correspond to one or more base stations. NR cells can be configured as access cells (ACells) or data-only cells (DCells). For example, the RAN (e.g., central unit or distributed unit) can configure cells. DCells can be cells used for carrier aggregation or dual connectivity, and cannot be used for initial access, cell selection / reselection, or handover. In some cases, DCells may not transmit synchronization signals (SS). In some cases, DCells may transmit SS. NR BS can send DL signals to the UE to indicate the cell type. Based on the cell type instruction, the UE can communicate with the NR BS. For example, the UE can determine the NR base station based on the indicated cell type to consider for cell selection, access, handover, and / or measurement.

[0048] Figure 3An example logical architecture of a distributed RAN 300 is illustrated according to various aspects of the present invention. A 5G access node (AN) 306 may include an access node controller (ANC) 302. The ANC may be the central unit (CU) of the distributed RAN 300. The backhaul interface to the next-generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface to the adjacent next-generation access node (NG-AN) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as a base station, NR base station, node B, 5G node B, AP, or some other terminology). As mentioned above, TRP can be used interchangeably with "cell".

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

[0050] The local architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. The architecture can be defined to support 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 LTE. Depending on various aspects, the NG-AN 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for both LTE and NR.

[0051] This architecture can enable collaboration between TRPs 308. For example, collaboration can be pre-configured within a TRP and / or across TRPs via ANC 302. Depending on the aspects, an inter-TRP interface may not be required or may not exist.

[0052] Depending on various factors, the dynamic configuration of separate logical functions can be achieved within a distributed RAN 300 architecture. PDCP, RLC, and MAC protocols can be adaptively placed in the ANC or TRP.

[0053] Figure 4An example physical architecture of a distributed RAN 400 is illustrated according to various aspects of the present invention. A centralized core network unit (C-CU) 402 can host core network functions. The C-CU can be deployed centrally. C-CU functions can be offloaded (e.g., to an advanced wireless service (AWS)) to handle peak capacity. A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can be deployed in a distributed manner. The C-RU can be located closer to the network edge. A DU 406 can host one or more TRPs. The DU can be located at the network edge with RF functionality.

[0054] Figure 5 This is a schematic diagram 500 illustrating an example of a DL-centered time slot. The DL-centered time slot may include a control section 502. The control section 502 may exist in the initial or beginning portion of the DL-centered time slot. The control section 502 may include various scheduling information and / or control information corresponding to the various portions of the DL-centered time slot. In some configurations, the control section 502 may be a PDCCH, such as... Figure 5 As shown, the DL-centric time slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-centric time slot. The DL data portion 504 may include communication resources for transmitting DL data from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 504 may be a PDSCH.

[0055] The DL-centered time slot may also include a shared UL portion 506. The shared UL portion 506 may sometimes be referred to as a UL burst, a shared UL burst, and / or various other suitable terms. The shared UL portion 506 may include feedback information corresponding to the various other portions of the DL-centered time slot. For example, the shared UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include ACK signals, NACK signals, HARQ indicators, and / or various other suitable types of information. The shared UL portion 506 may include additional or alternative information, such as information regarding the random access channel (RACH) process, scheduling requests (SR), and various other suitable types of information.

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

[0057] Figure 6 This is a schematic diagram 600 illustrating an example of a UL-centered time slot. The UL-centered time slot may include a control section 602. The control section 602 may be present at the beginning or start of the UL-centered time slot. Figure 6 The control section 602 in the reference above can be similar to the one mentioned above. Figure 5 The control section 502 is described. The UL-centric time slot may also include a UL data section 604. The UL data section 604 may sometimes be referred to as the payload of the UL-centric time slot. The UL section refers to the communication resources used to transmit UL data from a lower-level entity (e.g., the UE) to a scheduling entity (e.g., the UE or the BS). In some configurations, the control section 602 may be a PDCCH.

[0058] like Figure 6 As shown, the end of control section 602 may be time-separated from the start of UL data section 604. This time interval may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This interval provides time for switching from DL communication (e.g., receiving operations of a scheduling entity) to UL communication (e.g., transmitting operations of a scheduling entity). UL-centric time slots may also include a shared UL section 606. Figure 6 The common UL part 606 in the above is similar to the one mentioned above. Figure 5 The common UL portion 506 is described. The common UL portion 606 may additionally or alternatively include information regarding CQI, SRS, and various other suitable types of information. Those skilled in the art will understand that the foregoing is merely one example of a UL-centric time slot, and alternative structures with similar features may exist without departing from the various aspects described herein.

[0059] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using sidelink signaling. Practical applications of this type of sidelink communication can include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Everything (IoE) communication, IoT communication, mission-critical mesh, and / or various other suitable applications. Typically, sidelink signaling refers to the transmission of a signal from one subordinate entity (e.g., UE 1) to another (e.g., UE 2) without requiring relay communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity could be used for scheduling or control purposes. In some examples, licensed spectrum can be used to transmit sidelink signals (unlike wireless LANs, which typically use licensed spectrum).

[0060] In some configurations, according to the current Third Generation Partnership Project (3GPP) specifications, a User Equipment (UE) can maintain an equivalent network list, which can be an equivalent Public Land Mobile Network (PLMN) list or an equivalent Standalone Non-Public Network (SNPN) list. In this scenario, when the UE is in the process of registering or deregistering with a first network (e.g., a PLMN), if an event indicating an error or anomaly occurs during the registration or deregistration process (e.g., the UE receives reason #13 indicating roaming is not allowed in the tracking area, or the UE encounters a registration attempt counter equal to 5), the UE will typically delete the equivalent network list and perform a series of other operations (e.g., delete the last accessed registered Tracking Area Identifier (TAI) and TAI list, delete the 5G-GUTI and ngKSI, reset the registration attempt counter, etc.). However, once the equivalent network list is deleted, the UE will lose the opportunity to access the equivalent network in the future.

[0061] In view of these deficiencies, certain aspects of this disclosure relate to methods and apparatus for performing network denial or no response and processing equivalent PLMN or SNPN, wherein the UE can maintain the equivalent network list in response to an event (e.g., receiving reason #13 or encountering a registration attempt counter equal to 5) rather than always deleting the list, thereby allowing the UE to still have the opportunity to switch to other networks (e.g., equivalent PLMN or SNPN) based on the equivalent network list.

[0062] Figure 7 This is a schematic diagram illustrating an example process of a UE registering with the first access point of a first network. For example... Figure 7 As shown, UE 710 can be a UE or device supporting dual access services, and two base stations 720 and 725 provide two independent available accesses to a first network (e.g., a first PLMN). For example, base station 720 can be used for first access to the first PLMN, while base station 725 can be used for second access to the same first PLMN. In some configurations, one of the first and second accesses can be a 3GPP access (e.g., 5G NR) to the first PLMN, while the other can be a non-3GPP access (e.g., Wi-Fi) to the same first PLMN. In other words, one of base station 720 and base station 725 can be a 3GPP access (e.g., 5G NR) to the first PLMN, while the other can be a non-3GPP access (e.g., Wi-Fi) to the same first PLMN.

[0063] In example process 700, during operation 730, UE 710 maintains a single list of equivalent networks for the first network. In some configurations, this list of equivalent networks is a list of equivalent PLMNs or an equivalent SNPN. During operation 740, UE 710 is registering with base station 725 via / to a second access point of the first network or has already registered with base station 725 via / to a second access point of the first network. In this case, UE 710 may attempt to register with base station 720 via / to a first access point of the first network. For example, UE 710 may send a registration request message 750 to base station 720 during the initial registration process. During operation 755, upon receiving the registration request message 750 requesting service through the first access point, base station 720 may determine whether the registration request is accepted or rejected. For example, the first network (e.g., a first PLMN) may offer roaming service to UE 710 through subscription, but UE 710 may be located in a tracking area where the first PLMN does not offer roaming service. In this scenario, base station 720 can send a registration rejection message 760 to UE 710, containing reason #13, indicating that roaming is not permitted in the tracking area. In operation 770, UE 710 maintains a single equivalent network list without deleting it after receiving reason #13. In operation 780, UE 710 can perform other appropriate operations, such as deleting the last accessed registered TAI and the TAI list, deleting 5G-GUTI and ngKSI, resetting the registration attempt counter, and so on.

[0064] Figure 8 This is a schematic diagram illustrating an example process of a UE performing mobility and periodic updates for a first access to a first network. (Example) Figure 8As shown, similar to process 700, UE 810 can be a UE or device supporting dual access services, with two base stations 820 and 825 providing two independent available accesses to a first network (e.g., a first PLMN). For example, base station 820 can be used for first access to the first PLMN, while base station 825 can be used for second access to the same first PLMN. In some configurations, one of the first and second accesses can be a 3GPP access (e.g., 5G NR) to the first PLMN, while the other can be a non-3GPP access (e.g., Wi-Fi) to the same first PLMN. In other words, one of base stations 820 and 825 can be a 3GPP access (e.g., 5G NR) to the first PLMN, while the other can be a non-3GPP access (e.g., Wi-Fi) to the same first PLMN.

[0065] In example process 800, during operation 830, UE 810 maintains a single equivalent network list for the first network. In some configurations, the equivalent network list is an equivalent PLMN list or an equivalent SNPN list. During operation 840, UE 810 is registering with base station 825 via / to a second access point of the first network, or has already registered with base station 825 via / to a second access point of the first network. During operation 850, UE 810 is registering with base station 820 via / to a first access point of the first network, or has already registered with base station 820 via / to a first access point of the first network. In this case, UE 810 may attempt to periodically perform a mobility and periodic registration update process with base station 820 via / to the first access point of the first network. For example, UE 810 may send a mobility registration update (MRU) request message 860 to base station 820 during the mobility and periodic registration update process. In operation 865, after receiving an MRU request message 860 requesting service through the first access, base station 820 can determine whether the registration request is accepted or rejected. For example, the first network (e.g., the first PLMN) can determine that UE 810 is currently in a tracking area, thus preventing the first PLMN from providing roaming in that tracking area. In this case, base station 820 can send an MRU rejection message 868 to UE 810 with reason #13, where reason #13 indicates that roaming is not allowed in the tracking area. After receiving reason #13, in operation 870, UE 810 maintains a single equivalent network list without deleting it. In operation 880, UE 810 can perform other corresponding operations, such as deleting the last accessed registration TAI and TAI list, deleting 5G-GUTI and ngKSI, resetting the registration attempt counter, and so on.

[0066] Figure 9This diagram illustrates an example process of a UE performing a deregistration procedure in the first access of a first network. Figure 9 As shown, similar to processes 700 and 800, UE 910 can be a UE or device supporting dual access services, and two base stations 920 and 925 provide two independent available accesses to a first network (e.g., a first PLMN). For example, base station 920 can be the first access to the first PLMN, and base station 925 can be the second access to the same first PLMN. In some configurations, one of the first and second accesses can be a 3GPP access (e.g., 5G NR) to the first PLMN, while the other of the first and second accesses can be a non-3GPP access (e.g., Wi-Fi) to the same first PLMN. In other words, one of base stations 920 and 925 can be used for 3GPP access (e.g., 5G NR) to the first PLMN, while the other of base stations 920 and 925 can be used for non-3GPP access (e.g., Wi-Fi) to the same first PLMN.

[0067] In example process 900, in operation 930, UE 910 maintains a single list of equivalent networks for the first network. In some configurations, the list of equivalent networks is a list of equivalent PLMNs or an equivalent SNPN. In operation 940, UE 910 is registering to base station 925 via / to a second access of the first network, or has already registered to base station 925 via / to a second access of the first network. In operation 950, UE 910 is registering to base station 920 via / to a first access of the first network, or has already registered to base station 920 via / to a first access of the first network. In this case, base station 920 may determine that a deregistration process is required for UE 910 via the first access of the first network. For example, in operation 955, base station 920 may determine that a deregistration process is required because UE 910 is now in a tracking area, causing the first network (e.g., the first PLMN) to not provide roaming in that tracking area. In this scenario, base station 920 can send a deregistration request message 960 to UE 910 with reason #13, where reason #13 indicates that roaming is not permitted in the tracking area. Specifically, the deregistration request message 960 includes information indicating the type of deregistration for which re-registration for UE 910 is not required. Upon receiving reason #13, in operation 970, UE 910 maintains a single equivalent network list without deleting it. In operation 980, UE 910 can perform other appropriate operations, such as deleting the last accessed registration TAI and TAI list, deleting 5G-GUTI and ngKSI, resetting the registration attempt counter, and so on. In operation 990, UE 910 sends a deregistration confirmation (ACK) message 990 to base station 920.

[0068] Figure 10 This is a schematic diagram illustrating an example process between the UE and two access points of the first network. (Example) Figure 10 As shown, similar to processes 700, 800, and 900, UE 1010 can be a UE or device supporting dual access services, with two base stations 1020 and 1025 providing two independent accesses to a first network (e.g., a first PLMN). For example, base station 1020 can be used for first access to the first PLMN, and base station 1025 can be used for second access to the same first PLMN. In some configurations, one of the first and second accesses can be a 3GPP access (e.g., 5G NR) to the first PLMN, while the other of the first and second accesses can be a non-3GPP access (e.g., Wi-Fi) to the same first PLMN. In other words, one of base stations 1020 and 1025 can be used for 3GPP access (e.g., 5G NR) to the first PLMN, while the other of base stations 1020 and 1025 can be used for non-3GPP access (e.g., Wi-Fi) to the same first PLMN.

[0069] In example process 1000, in operation 1030, UE 1010 maintains a single equivalent network list for the first network. In some configurations, the equivalent network list is an equivalent PLMN list or an equivalent SNPN list. In operation 1040, UE 1010 is registering to base station 1025 via / to a second access of the first network or has already registered to base station 1025 via / to a second access of the first network. In this case, UE 1010 may attempt to register to base station 1020 via / to a first access of the first network. For example, UE 1010 may send a series of registration request messages 1050 to 1060 to base station 1020 during the initial registration process, and UE 1010 has a registration attempt counter for counting registration attempts. Specifically, the value of the registration attempt counter is incremented by 1 for each registration request message sent. In operation 1070, when the registration attempt counter equals 5 (indicating that 5 registration attempts have been made), UE 1010 maintains the single equivalent network list without deleting it. In operation 1080, UE 1010 can perform other corresponding operations, such as deleting the last accessed TAI and TAI list, deleting 5G-GUTI and ngKSI, resetting the registration attempt counter, and so on.

[0070] In each of processes 700, 800, 900, and 1000, the UE maintains a single equivalent network list for the first network, and retains this single equivalent network list when an event occurs during a registration or deregistration process through / to the first access of the first network (e.g., the UE receives reason #13 or encounters a registration attempt counter equal to 5). Specifically, even though an event indicates an anomaly has occurred during the first access of the first network, the UE remains registered in a second access of the first network. Therefore, maintaining a single equivalent network list for the first network gives the UE the opportunity to switch to other networks in the equivalent network list in the future, allowing for a wider range of UE mobility possibilities.

[0071] Figure 11 This is a flowchart illustrating an example process of a UE registering to two accesses on the same network. Process 1100 can be executed by the UE (e.g., UE 700, 800, 900, or 1000). Figure 11 As shown, in operation 1110, the UE maintains a single list of equivalent networks for the first network (e.g., the first PLMN). In operation 1120, the UE performs a registration or deregistration process via a first access point of the first network, where the UE is registering to a second access point of the same first network or the UE has already registered to a second access point of the same first network. For example, the first network is a PLMN, and the UE registers to the first PLMN via 5G NR and Wi-Fi as two access points. In the registration or deregistration process via / to the first access point, in operation 1130, the UE determines whether an event has occurred during the registration or deregistration process via / to the first access point of the first network, such as receiving reason #13 or encountering a registration attempt counter equal to 5. If no such event has occurred, the UE continues with the registration or deregistration process. If such an event has occurred during the registration or deregistration process, in operation 1140, the UE maintains a single list of equivalent networks without deleting the list. In other words, the UE maintains a list of equivalent PLMNs or equivalent SNPNs for the first PLMN.

[0072] In process 1100, the UE registers to two accesses to the same first network (e.g., the first PLMN). On the other hand, if the UE registers to two different networks using the corresponding access (e.g., two PLMNs or one PLMN and one SNPN), the UE does not need to maintain an equivalent network list for that network if an event occurs in the network access.

[0073] Figure 12 This is a flowchart illustrating an example process for a UE to register with two different networks. Process 1200 can be performed by the UE (e.g., UE 700, 800, 900, or 1000). Figure 12As shown, in operation 1210, the UE maintains a single list of equivalent networks for the first network (e.g., the first PLMN or the first SNPN). In operation 1220, the UE performs a registration or deregistration process via / to a first access of the first network, where the UE is registering via / to a second access of a second different network (e.g., a second different PLMN or SNPN), or the UE has already registered via / to a second access of the second network. For example, the first network is the first PLMN, the second network is the second PLMN, and the UE registers to the first PLMN via 5G NR and to the second PLMN via Wi-Fi. In the registration or deregistration process via / to the first access of the first network, in operation 1230, the UE determines whether an event has occurred during the registration or deregistration process via the first access of the first network, such as receiving reason #13 or encountering a registration attempt counter equal to 5. If no such event has occurred, the UE continues with the registration or deregistration process. If such an event occurs during the registration or deregistration process, in operation 1240, the UE can delete the single equivalent network list for the first network, that is, delete the equivalent PLMN or equivalent SNPN list for the first PLMN.

[0074] Figure 13 This is a flowchart of a method (procedure) for UE wireless communication. Procedure 1300 can be executed by the UE (e.g., UE700, 800, 900, or 1000). Figure 13 As shown, in operation 1310, the UE maintains a single list of equivalent networks for the first network. In operation 1320, the UE performs a registration or deregistration process through a first access point of the first network, wherein the UE is registering to a second access point of the same first network, or the UE has already registered to a second access point of the same first network. In operation 1330, during the registration or deregistration process, in response to events in the registration or deregistration process, the UE maintains a single list of equivalent networks.

[0075] In some configurations, the first network is either a PLMN or an SNPN, and the equivalent network list is either an equivalent PLMN list or an equivalent SNPN list.

[0076] In some configurations, one of the first and second access methods is a 3GPP access method, and the other is a non-3GPP access method.

[0077] In some configurations, the event includes receiving reason #13 in a downlink NAS message via first access, where reason #13 indicates that roaming is not permitted in the tracking area. In one embodiment, reason #13 is received in a registration rejection message during the initial registration process or during a mobility and periodic registration update process. In one embodiment, reason #13 is received in a deregistration request message, and the deregistration request message includes information indicating the type of deregistration that does not require re-registration.

[0078] In some configurations, this event includes: encountering a registration attempt counter equal to 5. In one embodiment, the registration attempt counter is equal to 5 during the initial registration process or during mobility and periodic registration update processes.

[0079] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is an example of an exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0080] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent 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 be limited to the aspects shown herein, but should be given the full scope consistent with the text of the claims, wherein, unless expressly stated, references to elements in the singular form are not intended to mean “one and only one,” but rather “one or more.” The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term “some” means one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of 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, phrases such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described herein, as known or will be known by those skilled in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. Terms such as "module," "mechanism," "element," and "device" may not replace the term "apparatus." Therefore, unless a claim element is explicitly stated using the phrase "apparatus for...", no claim element should be construed as an apparatus plus a function.

Claims

1. A method for wireless communication of a user equipment, comprising: Maintain a single list of equivalent networks for the first network; The user equipment (UE) performs a registration or deregistration process on the first network via a first access point, wherein the UE is registering to the first network via a second access point, or the UE has already registered to the first network via the second access point; and The single equivalent network list is maintained in response to events during the registration or deregistration process.

2. The method of claim 1, wherein, The first network is a public land mobile network, and the equivalent network list is an equivalent PLMN list, or The first network is an independent, non-public network, and the equivalent network list is an equivalent SNPN list.

3. The method of claim 1, wherein one of the first access and the second access is a 3GPP access, and the other of the first access and the second access is a non-3GPP access.

4. The method of claim 1, wherein, The event includes: The reason is received in the downlink non-access stratum message through the first access, wherein the reason indicates that roaming is not allowed in the tracking area of ​​the user equipment.

5. The method of claim 4, wherein, The reason is received in the registration rejection message during the initial registration process or during the mobility and periodic registration update process.

6. The method of claim 4, wherein, The reason is received in the deregistration request message, which includes information indicating the type of deregistration that does not require re-registration.

7. The method of claim 1, wherein, The event includes: The registration attempt counter is 5.

8. The method of claim 7, wherein, The registration attempt counter is equal to 5 during the initial registration process or during the mobility and periodic registration update process.

9. An apparatus for wireless communication, the apparatus being a user equipment, comprising: Memory; as well as At least one processor coupled to the memory, the processor being configured to: Maintain a single list of equivalent networks for the first network; The user equipment (UE) performs a registration or deregistration process on the first network via a first access point, wherein the UE is registering to the first network via a second access point, or the UE has already registered to the first network via the second access point; and The single equivalent network list is maintained in response to events during the registration or deregistration process.

10. The apparatus of claim 9, wherein, The first network is a public land mobile network, and the equivalent network list is an equivalent PLMN list, or The first network is an independent, non-public network, and the equivalent network list is an equivalent SNPN list.

11. The apparatus of claim 9, wherein, One of the first access and the second access is a 3GPP access, and the other of the first access and the second access is a non-3GPP access.

12. The apparatus of claim 9, wherein, The event includes: The reason is received in the downlink non-access stratum message through the first access, wherein the reason indicates that roaming is not allowed in the tracking area of ​​the user equipment.

13. The apparatus of claim 12, wherein, The reason is received in the registration rejection message during the initial registration process or during the mobility and periodic registration update process.

14. The apparatus of claim 12, wherein, The reason is received in the deregistration request message, which includes information indicating the type of deregistration that does not require re-registration.

15. The apparatus of claim 9, wherein, The event includes: The registration attempt counter is 5.

16. The apparatus of claim 15, wherein, The registration attempt counter is equal to 5 during the initial registration process or during the mobility and periodic registration update process.

17. A computer-readable medium storing computer-executable code for wireless communication in a mobile device, comprising the code to: Maintain a single list of equivalent networks for the first network; The user equipment (UE) performs a registration or deregistration process on the first network via a first access point, wherein the UE is registering to the first network via a second access point, or the UE has already registered to the first network via the second access point; and The single equivalent network list is maintained in response to events during the registration or deregistration process.

18. The computer-readable medium of claim 17, wherein, The first network is a public land mobile network, and the equivalent network list is an equivalent PLMN list, or The first network is an independent, non-public network, and the equivalent network list is an equivalent SNPN list.

19. The computer-readable medium of claim 17, wherein, One of the first network access and the second access is a 3GPP access, and the other of the first access and the second network access is a non-3GPP access.

20. The computer-readable medium of claim 17, wherein, The event includes one of the following: The reason is received in the downlink non-access stratum message via the first access, wherein the reason indicates that roaming is not permitted in the tracking area of ​​the user equipment; or The registration attempt counter is 5.

Images