Wireless communication method of user equipment (UE) and equipment for wireless communication

By aborting the 5G mobility management process in abnormal situations and reselecting the network, the 5G NR technology solves the service interruption and performance degradation when dealing with localized service changes, achieving higher network adaptability and service stability. .

CN119095125APending Publication Date: 2024-12-06MEDIATEK SINGAPORE PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410729763.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-06-04
Filing Date
2024-06-06
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

When existing 5G NR technology deals with localized service changes, user equipment finds it difficult to effectively respond and switch networks when encountering abnormal situations, resulting in service interruption or performance degradation.

Method used

When an abnormal situation is detected, the user equipment aborts the current 5G mobility management process, resets the counter, stops the timer, releases the NAS signaling connection, and enters the public land mobile network search state to select a new non-public network.

Benefits of technology

It improves the flexibility and adaptability of user equipment in the face of localized service changes, ensures service continuity and performance stability, and enhances the efficiency of network selection and handover.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095125A_ABST
    Figure CN119095125A_ABST
Patent Text Reader

Abstract

The invention provides a wireless communication method of user equipment (UE) and equipment for wireless communication. The method may be performed by a user equipment (UE). In certain configurations, the UE initiates a first 5G Mobility Management, 5GMM, procedure on a first independent non-public network, SNPN, providing localized services. In response to the first event, the UE performs one or more operations including aborting the first 5GMM procedure, resetting a respective procedure attempt counter of the first 5GMM procedure, aborting a respective timer of the first 5GMM procedure, releasing a non-access stratum (NAS) signaling connection locally if there is the NAS signaling connection, and entering a Public Land Mobile Network (PLMN) search state to perform the SNPN selection procedure.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a communication system, and more particularly, to a technical method and device for processing localized service changes. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies to support communications with multiple users by sharing the available system resources. Examples of these 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.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, regional, or even global scale. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution driven by the 3rd Generation Partnership Project (3GPP) to meet new demands related to latency, reliability, security, scalability (e.g., Internet of Things (IoT)), and other requirements. Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements may also be applicable to other multiple access technologies and the telecommunication standards that adopt these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all intended aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate 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 that is presented later.

[0005] The present invention aims to provide a method and user equipment, which are technical methods and equipment for processing changes in localized services.

[0006] According to an embodiment of the present invention, a method, a computer-readable medium and a device are provided. The method can be performed by a user equipment UE. In certain configurations, the UE starts a first 5G mobility management 5GMM process on a first independent non-public network SNPN. In response to the first event, the UE performs one or more operations, including: terminating the first 5GMM process, resetting the corresponding process attempt counter of the first 5GMM process, stopping the corresponding timer of the first 5GMM process, releasing the NAS signaling connection locally if there is a non-access layer NAS signaling connection, and entering the public land mobile network PLMN search state to perform the SNPN selection process.

[0007] To accomplish the foregoing and related ends, the features included in one or more aspects and specifically pointed out in the claims are fully described below. The following description and the accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are indicative of several of the various ways of employing the principles of the various aspects, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is an example diagram of a wireless communication system and access network.

[0009] Figure 2 is a schematic diagram of a base station communicating with a UE in an access network.

[0010] Figure 3 An example logical architecture of a distributed access network is presented.

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

[0012] Figure 5 is a diagram showing an example of a downlink-dominated time slot.

[0013] Figure 6 is a diagram showing an example of an uplink-dominated time slot.

[0014] Figure 7 is a diagram showing a communication system with PLMN, SNPN and PNO-NPN / CAG providing localized service access.

[0015] Figure 8 is a flow chart of an example UE process.

[0016] Fig. 9 is an example process diagram of a UE during the initial registration process.

[0017] Fig.10 is an example process diagram of a UE during the initial registration process.

[0018] Fig.11 is an example process diagram of a UE during the initial registration process.

[0019] Fig.12 is an example process diagram of a UE during the initial registration process.

[0020] Fig.13 The figure is an example process diagram of a UE in the mobility registration update process.

[0021] Fig.14 It is an example process diagram of a UE in the service request process.

[0022] Fig.15 is a flow chart of an example UE process.

[0023] Fig.16 is a flow chart of an example UE process.

[0024] Fig.17 The present invention is a flowchart of a UE wireless communication method (process). DETAILED DESCRIPTION

[0025] The technical terms in this specification are used in the technical field. If there is an explanation or definition of certain technical terms in this specification, the technical terms in this part will take precedence over the explanation or definition elsewhere. The present invention of each embodiment has one or more technical features. Where possible, a person of ordinary skill in the art can selectively implement some or all of the technical features of the present invention, or selectively combine these technical features of the present invention.

[0026] Figure 1 is a diagram of an exemplary 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, user equipment (UEs) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a home cell, a micro cell, and a medium cell.

[0027] Base stations 102 configured as 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a backend link 132 (e.g., an S1 interface). Base stations 102 configured as 5GNR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a backend link 184. Among other functions, base stations 102 can 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, non-access stratum (NAS) message distribution, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and warning messaging. The base stations 102 can communicate with each other directly or indirectly (e.g., through EPC 160 or core network 190) via a backend link 134 (e.g., an X2 interface). The backend link 134 may be wired or wireless.

[0028] Base stations 102 may communicate wirelessly with user equipment (UEs) 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group called a Closed Subscriber Group (CSG). A communication link 120 between a base station 102 and user equipment (UEs) 104 may include uplink (UL) (also referred to as reverse link) transmissions from the user equipment (UE) 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the user equipment (UE) 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be carried out over one or more carriers. The base station 102 / user equipment (UEs) 104 may use spectrum with a bandwidth of up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz), with each carrier allocated in a carrier aggregation of a total of Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent or non-adjacent. For DL ​​and UL, the allocation of carriers may be asymmetric (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carriers may include one primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0029] Certain user equipments (UEs) 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed via various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

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

[0031] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' can adopt New Radio (NR) and use the same 5 GHz unlicensed spectrum as the Wi-Fi AP 150. The small cell 102' operating in the unlicensed spectrum with NR can enhance coverage and / or increase capacity of the access network.

[0032] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an evolved NodeB (eNB), a gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, may communicate with UE 104 in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near millimeter wave frequencies. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. Extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. The range of extremely high frequency is 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. Radio waves in this frequency band may be referred to as millimeter waves. Near millimeter waves may extend to frequencies of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communication using the millimeter wave / near millimeter wave radio frequency band (e.g., 3 GHz-300 GHz) has extremely high path loss and short distances. The mmWave base station 180 may communicate with the UE 104 using beamforming 182 to compensate for the extremely high path loss and short range.

[0033] The base station 180 may transmit beamformed signals in one or more transmit directions 108a to the UE 104. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for the base station 180 / UE 104. The transmit and receive directions of the base station 180 may be the same or different. The transmit and receive directions of the UE 104 may be the same or different.

[0034] The Evolved Packet Core (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. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide the functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and start MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a broadcast multicast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[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 may communicate with a unified data management (UDM) 196. The AMF 192 is a 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 is connected to the IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming media service, and / or other IP services.

[0036] Base stations may also be referred to as gNBs, Node Bs, evolved Node Bs (eNBs), access points, base transceiver stations, wireless base stations, wireless transceiver stations, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmission reception points (TRPs), or other suitable terms. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, 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, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs 104 may be referred to as Internet of Things (IoT) devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a user agent, a mobile client, a client, or other suitable terminology.

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

[0038] Figure 22 is a block diagram of a base station 210 communicating with a user equipment (UE) 250 in an access network. In the downlink (DL), IP packets from the evolved core (EPC) 160 may be provided to the controller / processor 275. The controller / processor 275 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 275 provides RRC layer functions associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), 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; PDCP layer functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmitting upper layer packet data units (PDUs), error correction through automatic repeat request (ARQ), splicing, segmentation and reassembly of RLC service data units (SDUs), re-segmentation 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), MAC Demultiplexing of SDUs from TBs, scheduling information reporting, error correction through Hybrid Automatic Repeat Request (HARQ), priority handling and MAC layer functions related to logical channel priority.

[0039] The transmit (TX) processor 216 and the 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 of transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and multiple-input multiple-output (MIMO) antenna processing. The TX processor 216 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 274 may be used to determine coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback transmitted by UE 250. Each spatial stream may then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0040] At the UE 250, each receiver 254RX receives a signal through its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functions associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams intended for the UE 250. If multiple spatial streams are intended for the UE 250, they may be combined into a single OFDM symbol stream by the RX processor 256. The RX processor 256 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 210. These soft decisions may be based on channel estimates calculated by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 210 on the physical channel. The data and control signals are then provided to the controller / processor 259 which implements Layer 3 and Layer 2 functions.

[0041] The controller / processor 259 may be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer-readable medium. In the uplink (UL), the controller / processor 259 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 259 is also responsible for error detection using an acknowledgement (ACK) and / or negative acknowledgement (NACK) protocol to support HARQ operations.

[0042] Similar to the functional description associated with DL transmission of the base station 210, the controller / processor 259 provides RRC layer functions associated with system information (e.g., MIB, SIBs) acquisition, RRC connection and measurement reporting; PDCP layer functions associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, splicing, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel priority.

[0043] Channel estimates derived by the channel estimator 258 from a reference signal or feedback transmitted by the base station 210 may be used by the TX processor 268 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antennas 252 through separate transmitters 254TX. Each transmitter 254TX may modulate a radio frequency carrier with a corresponding spatial stream for transmission. UL transmissions are processed at the base station 210 in a manner similar to that associated with the receiver function of the UE 250. Each receiver 218RX receives a signal through its corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the radio frequency carrier and provides the information to the RX processor 270.

[0044] The controller / processor 275 may be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer readable medium. In the uplink, the controller / processor 275 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the user equipment (UE) 250. The 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 an ACK and / or NACK protocol to support hybrid automatic repeat request (HARQ) operations.

[0045] New Radio (NR) may refer to a radio configured according to a new air interface (e.g., a non-orthogonal frequency division multiple access (OFDMA) air interface) or a fixed transport layer (e.g., non-Internet Protocol (IP)). NR may use orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) in uplink and downlink, and may include support for half-duplex operation using time division duplex (TDD). NR may include enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., above 80 MHz), millimeter wave (mmW) targeting high carrier frequencies (e.g., 60 GHz), massive machine type communications (mMTC) targeting non-backward compatible MTC technologies, and / or mission critical targeting ultra-reliable low latency communications (URLLC) services.

[0046] A single component carrier bandwidth of 100MHz can be supported. In one example, an NR resource block (RB) can span 12 subcarriers with a subcarrier bandwidth of 60kHz and a duration of 0.25ms, or a bandwidth of 30kHz and a duration of 0.5ms (similarly, a 15kHz subcarrier spacing (SCS) has a bandwidth of 50MHz over a 1ms duration). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR time slots) with a length of 10ms. Each time slot can indicate the link direction of data transmission (i.e., downlink or uplink), and the link direction of each time slot can be switched dynamically. Each time slot can include downlink / uplink data and downlink / uplink control data. NR's uplink and downlink time slots can be as follows: Figure 5 and Figure 6 The described in more detail.

[0047] The NR radio access network (RAN) may include a central unit (CU) and a distributed unit (DU). NR base stations (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. DCells may be cells for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or switching. In some cases, DCells may not transmit a synchronization signal (SS), and in some cases, DCells may transmit SS. The NR base station may transmit a downlink signal indicating the cell type to the UE. Based on the cell type indication, the UE may communicate with the NR base station. For example, the UE may determine the NR base station to be considered for cell selection, access, switching, and / or measurement based on the indicated cell type.

[0048] Figure 3 An example logical architecture of a distributed RAN 300 according to aspects of the present disclosure is shown. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be a central unit (CU) of the distributed RAN. The backhaul interface to the next generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface to adjacent next generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (also referred to as base stations, NR base stations, Node Bs, 5GNBs, APs, or other terms). As described above, TRPs may be used interchangeably with "cells."

[0049] The TRP 308 may be a distributed unit (DU). The TRP may be connected to one ANC (ANC 302) or multiple ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, the TRP may be connected to multiple ANCs. The TRP may include one or more antenna ports. The TRP may be configured to provide traffic services to the UE individually (e.g., dynamically selected) or jointly (e.g., joint transmission).

[0050] The local architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. The architecture can define fronthaul solutions that support 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. According to aspects, the next generation access node (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.

[0051] The architecture may enable collaboration between and among TRPs 308. For example, collaboration may be provisioned within a TRP and / or performed across TRPs by ANC 302. Depending on the aspect, an inter-TRP interface may not be required / present.

[0052] According to aspects, there may be dynamic configuration of logical functional partitioning within the architecture of the distributed RAN 300. PDCP, RLC, MAC protocols may be adaptively placed in the ANC or TRP.

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

[0054] Figure 5 500, illustrating an example downlink (DL)-centric time slot. The DL-centric time slot may include a control portion 502. The control portion 502 may be present at an initial or beginning portion of the DL-centric time slot. The control portion 502 may include various scheduling information and / or control information corresponding to various portions of the DL-centric time slot. In some configurations, the control portion 502 may be a physical downlink control channel (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 is sometimes also referred to as the payload of the DL-centric time slot. The DL data portion 504 may include communication resources for communicating DL data from a scheduling entity (e.g., a UE or a base station BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 504 may be a physical downlink shared channel (PDSCH).

[0055] The DL-centric timeslot may also include a common uplink (UL) portion 506. The common UL portion 506 is sometimes referred to as a UL burst, a common UL burst, and / or other appropriate terms. The common UL portion 506 may include feedback information corresponding to various other portions of the DL-centric timeslot. For example, the common UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include an acknowledgment signal ACK, a negative acknowledgement signal NACK, a HARQ indicator, and / or other appropriate types of information. The common UL portion 506 may include additional or alternative information, such as information related to a random access channel (RACH) procedure, scheduling requests (SRs), and various other appropriate types of information.

[0056] like Figure 5 As shown, the end of the DL data portion 504 may be separated in time from the beginning of the common UL portion 506. This time separation is sometimes referred to as a gap, a guard period, a guard interval, and / or other appropriate terminology. This separation provides a switching time from DL communication (e.g., a reception operation of a subordinate entity (e.g., a UE)) to UL communication (e.g., a transmission of a subordinate entity (e.g., a UE)). Those of ordinary skill in the art will appreciate that the above is merely an example of a DL-centric time slot, and there may be alternative structures with similar features without necessarily departing from the aspects described herein.

[0057] Figure 6 600, illustrating an example uplink (UL) centric timeslot. The UL centric timeslot may include a control portion 602. The control portion 602 may be present at the beginning or start of the UL centric timeslot. Figure 6 The control portion 602 in the above reference may be Figure 5 The control portion 502 is similarly described. The UL-centric time slot may also include a UL data portion 604. The UL data portion 604 is sometimes also referred to as the payload of the UL-centric time slot. The UL portion may refer to communication resources used to communicate UL 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).

[0058] like Figure 6 As shown, the end of the control portion 602 may be separated in time from the beginning of the UL data portion 604. This time separation is sometimes referred to as a gap, a guard period, a guard interval, and / or other appropriate terminology. This separation provides time to switch from DL communications (e.g., reception operations of the scheduling entity) to UL communications (e.g., transmissions of the scheduling entity). The UL-centric timeslot may also include a common UL portion 606. Figure 6The common UL portion 606 in the above reference may be Figure 5 The common UL portion 606 may also include information related to a channel quality indicator (CQI), a sounding reference signal (SRSs), and various other suitable types of information. One of ordinary skill in the art will appreciate that the above is merely an example of a UL-centric time slot, and that there may be alternative structures with similar features without necessarily departing from the aspects described herein.

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

[0060] A Public Land Mobile Network (PLMN) is a network established and operated by an administration or recognized operating organization (ROA) specifically for the provision of land mobile communication services to the public. PLMN provides communication possibilities for mobile users. PLMN can provide services in one or more frequency bands. Access to PLMN services is achieved through an air interface involving radio communications between mobile phones and base stations, as well as integrated IP network services. A PLMN may include multiple radio access networks (RANs) that access mobile services using different radio access technologies (RATs). The radio access network is the part of a mobile communication system that implements the radio access technology. Conceptually, the RAN is located between mobile devices and provides connectivity to its core network (CN). According to the standards, mobile phones and other wirelessly connected devices are referred to as user equipment (UE, i.e. MS), terminal equipment (TE), mobile station (MS, i.e. UE), mobile terminal (MT), etc. Examples of different RATs include 2G GERAN (GSM) radio access network, 3G UTRAN (UMTS) radio access network, 4G E-UTRAN (LTE), 5G New Radio (NR) radio access network, Next Generation RAN (NG-RAN), and other non-3GPP access RATs including WiFi.

[0061] In contrast to PLMN, a non-public network (NPN) is a network used for non-public purposes. An NPN is either a standalone non-public network (SNPN), i.e., operated by an NPN operator and not dependent on the network functionality provided by the PLMN, or a public network integrated NPN (PNI-NPN), i.e., a non-public network deployed with the support of a PLMN. A credential holder (CH) can authenticate and authorize access to a SNPN that is separate from the credential holder. The combination of a PLMN ID and a network identifier (NID) identifies a SNPN. A UE may be enabled to support SNPNs.

[0062] A PNI-NPN is an NPN provided over a PLMN, for example, over a dedicated DNN or one or more network slice instances assigned to the NPN. When a PNI-NPN is provided over a PLMN, the UE must subscribe to the PLMN to access the PNI-NPN. Since network slicing cannot prevent a UE from attempting to access the network in an area where the network slice assigned to the NPN is not allowed, access control can be performed on the PNI-NPN using a closed access group (CAG). A closed access group (CAG) identifies a set of subscribers that are allowed to access one or more CAG cells associated with the CAG. A CAG is used for a PNI-NPN to prevent UEs that are not allowed to access the NPN over the associated cells from automatically selecting and accessing the associated CAG cells. CAGs are used for access control, for example, for authorization at cell selection time and configured as part of mobility restrictions in a subscription. A CAG is identified by a CAG identifier that is unique within the PLMN ID range.

[0063] Local or localized services are localized services (e.g., provided in a specific / limited area and / or limited in time). A localized service provider is an application provider or network operator that localizes its services and provides them to the end-user over a hosted network. A hosted network is a network that provides localized services (access), a hosted network can be a SNPN or a PNI-NPN, and a home network is a network that has a subscription or credentials currently used by the UE. A home network can be a Home-PLMN or a Subscribed-SNPN. The end-user can enable or disable access to localized services. If the end-user disables access to localized services, the UE (i.e., MS) may not be able to access the NPN that provides localized services.

[0064] In order to provide the UE with access to localized services, the UE needs to be able to discover, select and access an NPN (as a hosting network) that provides localized services.

[0065] Figure 7 FIG. 7 is a schematic diagram of a communication system 700 having a PLMN 710, a SNPN 720, and a public network integrated NPN (PNI-NPN) / CAG 730 providing localized service access. Figure 7 As shown, the PLMN network 710 includes a control plane function, a user plane function (e.g., UPF), and an application that provides various services by communicating with multiple user equipments (UEs) including UE 701. A serving base station (e.g., gNB) 712 is part of a radio access network (RAN) 740. RAN 740 provides wireless access to UE 701 via RAT. An access and mobility management function (AMF) in PLMN 710 communicates with gNB 712. UE 701 may be equipped with a radio frequency (RF) transceiver or multiple RF transceivers.

[0066] The SNPN network 720 includes control plane functions, user plane functions (e.g., UPF), and applications that provide various services by communicating with multiple UEs including UE 701. A combination of a PLMN ID and a network identifier (NID) identifies a SNPN. A serving base station (e.g., gNB) 722 is part of the RAN 750. The RAN 750 provides radio access to the UE 701 via a RAT. The AMF in the SNPN 720 communicates with the gNB 722. The SNPN 720 is operated by an NPN operator and does not rely on network functions provided by the public network. A credential holder (CH) can authenticate and authorize access to the SNPN independently of the CH. The NG-RAN node that provides access to the SNPN broadcasts the following information: one or more PLMN IDs, and a list of NIDs for each PLMN ID, identifying the non-public networks (723) to which the NG-RAN provides access. The UE supporting SNPN is configured with the PLMN ID and NID (SNPNID) of the subscribed SNPN, and the UE supporting SNPN that supports accessing the SNPN using the credentials of the credential holder may also be configured with information for SNPN selection and registration (SNPN selection information or configuration), using SNPN subscription or using PLMN subscription (USIM) (in SNPN access mode) (702).

[0067] The PNI-NPN (CAG) network 730 includes a control plane function (which is optional because it may rely on the control plane function of the PLMN), a user plane function (which is optional because it may rely on the user plane function of the PLMN), and an application that provides various services by communicating with multiple UEs including UE 701. The PNI-NPN (CAG) 730 is a non-public network deployed with the support of the PLMN, for example, by sharing the RAN / gNB 712 and the control plane function. The CAG identifies a group of subscribers that are allowed to access one or more CAG cells associated with the CAG. The CAG is used for the PNI-NPN to prevent UEs that are not allowed to access the NPN through the associated cells from automatically selecting and accessing the associated CAG cells. The CAG is identified by a CAG identifier that is unique within the PLMN ID range. The CAG cell broadcasts one or more CAG identifiers per PLMN (113), and the UE is configured with CAG related configuration / information (e.g., an (enhanced) CAG information list containing a list of CAGs allowed per PLMN) (702).

[0068] Local or localized services are services that are localized (i.e., provided in a specific / limited area and / or limited in time (specific period of time)). A localized service provider is an application provider or network operator that localizes its services and provides them to the end-user over a hosted network. A hosted network is the network that provides access to localized services and can be either a SNPN or a PNI-NPN, while a home network is the network that has the subscription or credentials currently used by the UE. Figure 7 In the example of , both SNPN 720 and PNI-NPN (CAG) 730 may be hosted networks that provide localized service access to UE 701.

[0069] When the localization service in the network is completed, all user equipment (UE) registered with the network is expected to be moved to other networks or other cells within the same network. The other network can be a HPLMN, a VPLMN or another SNPN. The UE may stop using network resources for localization services due to a variety of reasons, such as: (a) the localization service in the network is completed; (b) the network selection validity condition information is no longer satisfied; (c) the user decides to stop using the localization service before the localization service is completed (for example, the end user disables access to the localization service); or (d) the network makes a policy decision that causes the UE to be deregistered before the localization service is completed. Validity information or restrictions or criteria or conditions (703) are provided or configured to the UE as part of the localization service information to restrict the UE from accessing the SNPN / PNI-NPN (as a hosting network) that provides localization services. In order to provide localization services to the UE, the UE needs to be able to discover, select and access the SNPN / PNI-NPN (as a hosting network) that provides localization services. The discovery mechanism is based on providing or configuring appropriate information for the UE.

[0070] Figure 88 is a flowchart of an example process of a UE. The example process can be performed by a UE (e.g., UE 701). At operation 810, the UE initiates a first 5GMM process on a first SNPN that provides localized services. Specifically, the first SNPN is selected according to clause a0) of clause 4.9.3.1.1 in 3GPP TS23.122 (i.e., the first SNPN provides localized services to the UE). In some embodiments, the first 5GMM process may be an initial registration process or a mobility registration update process. Alternatively, the first 5GMM process may be a service request process. It should be noted that the first 5GMM process is not a process for emergency services, nor is it a process for initiating a packet data unit (PDU) session for emergency services, where the request type of the initiation process is set to an existing emergency PDU session. At operation 820, during the first 5GMM process, the UE may encounter a first event, in which an abnormal situation occurs. When the first event occurs, localized service access in the first SNPN is no longer allowed for the UE. Examples of the first event may include, but are not limited to: timeout of a corresponding timer, receiving a rejection message with an abnormal or unexpected cause value, receiving information from a lower layer indicating a lower layer failure or a release of a NAS signaling connection, a change in the current tracking area identifier (TAI), a failure in the transmission of a NAS message, and receiving information from a lower layer indicating that an access attempt is prohibited. Optionally, the first event may include satisfying a condition, and the condition is: localized service access in the first SNPN is disabled; or the validity information of the first SNPN is no longer satisfied. In response to the first event (i.e., the occurrence of an abnormal situation), the localized service access in the first SNPN is no longer allowed for the UE. At operation 830, in response to the first event, the UE performs one or more operations, including: terminating the first registration process, resetting the corresponding process attempt counter of the first registration process, stopping the corresponding timer of the first registration process, locally releasing the NAS signaling connection if there is a NAS signaling connection, and entering a PLMN search state to perform an SNPN selection process. In some embodiments, the UE may perform one or more operations in response to the first event as soon as possible. Alternatively, in some embodiments, the UE may perform one or more operations in response to the first event later.

[0071] Fig. 9 FIG. 1 is a diagram illustrating an example process of the UE during the initial registration process. Fig. 9As shown, in example process 900, UE 902 (e.g., UE 701) sends an initial registration request 910 to base station 904 (e.g., gNB 722) to initiate an initial registration process for a selected SNPN. In particular, the selected SNPN is selected according to clause 4.9.3.1.1 a0) of 3GPP TS23.122 (i.e., the selected SNPN provides localized services to UE 902). In addition, the initial registration request 910 is not for emergency services and / or is not for initiating an emergency service PDU session with the request type set to "existing emergency PDU session".

[0072] Once the UE 902 sends the initial registration request 910, the UE 902 starts the timer T3510 920. The timer T3510 is a registration timer corresponding to the 5GMM registration process. Specifically, when the UE 902 sends a REGISTRATION REQUEST message (e.g., the initial registration request 910), the UE 902 starts the timer T3510 920. In a normal stop situation, when the UE 902 receives a REGISTRATION ACCEPT message (indicating that the registration request is accepted) or a REGISTRATION REJECT message (indicating that the registration request is rejected) from the network (e.g., the base station 904), the UE 902 will stop the timer T3510 920. However, if a timeout 925 of the timer T3510 920 occurs, such as Fig. 9 If the following error message is displayed, an abnormal situation may have occurred.

[0073] When the timeout 925 of the timer T3510 920 occurs, the UE 902 determines that the first event occurs. Optionally, the UE 902 may also determine whether a condition is satisfied (e.g., localized service access in the selected SNPN is disabled; or the validity information of the selected SNPN is no longer satisfied). If the first event occurs, and optionally the condition is satisfied, the UE 902 may perform one or more operations in response to the first event (e.g., the timeout 925 of the timer T3510 920). Fig. 9 As shown, UE 902 aborts the initial registration process 930, resets the corresponding registration attempt counter 940, and enters the PLMN search state 950 to perform the SNPN selection process.

[0074] Fig.10 FIG. 1 is a diagram illustrating an example process of the UE during the initial registration process. Fig.10As shown, in example process 1000, similar to example process 900, UE 1002 (e.g., UE 701) sends an initial registration request 1010 to base station 1004 (e.g., gNB 722) to initiate an initial registration process for a selected SNPN. In particular, the selected SNPN is selected according to clause 4.9.3.1.1 a0) of 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to UE 1002). In addition, the initial registration request 1010 is not for emergency services and / or is not for initiating an emergency service PDU session with a request type set to "existing emergency PDU session".

[0075] Once the user equipment (UE) 1002 sends the initial registration request 1010, the UE 1002 starts timer T35101020. Subsequently, the UE 1002 may receive a registration reject message 1025 from the base station 1004, and the registration reject message 1025 may include an abnormal / unexpected cause value, indicating that an abnormal situation has occurred. When the UE 1002 receives the registration reject message 1025 with the abnormal / unexpected cause value, the UE 1002 determines that the first event has occurred. Optionally, the UE 1002 may also determine whether a condition is met (for example, localized service access in the selected SNPN is disabled; or the validity information of the selected SNPN is no longer met). If the first event occurs, and optionally the condition is met, the UE 1002 may perform one or more operations in response to the first event (for example, receiving a registration reject message 1025 with an abnormal / unexpected cause value). Fig.10 As shown, UE 1002 stops timer T3510 1028, aborts the initial registration process 1030, resets the corresponding registration attempt counter 1040, and enters the PLMN search state 1050 to perform the SNPN selection process.

[0076] Fig.11 is an example diagram showing an example procedure of the UE during the initial registration process. Fig.11 As shown, in example procedure 1100, which is similar to example procedure 1000, UE 1102 (e.g., UE 701) sends an initial registration request 1110 to base station 1104 (e.g., gNB 722) to initiate an initial registration process for a selected SNPN. In particular, the selected SNPN is selected according to clause 4.9.3.1.1 a0) specified in 3GPP TS23.122 (i.e., the selected SNPN provides localized services for UE 1102). In addition, the initial registration request 1110 is not for emergency services and / or is not a process in which the PDU session initiation request type for emergency services is set to "existing emergency PDU session". In addition, UE 1102 may be in a NAS signaling connection.

[0077] Once UE 1102 sends the initial registration request 1110, UE 1102 starts timer T3510 1120. Subsequently, UE 1102 may receive a message from a lower layer indicating a lower layer failure or a NAS signaling connection release. When UE 1102 receives a message from a lower layer indicating a lower layer failure or a NAS signaling connection release, UE 1102 determines that a first event has occurred (i.e., an abnormal situation has occurred). Optionally, UE 1102 may also determine whether a condition is met (e.g., localized service access in the selected SNPN is disabled; or the validity information of the selected SNPN is no longer met). If the first event occurs, and optionally the condition is met, UE 1102 may perform one or more operations in response to the first event (e.g., receiving a message from a lower layer indicating a lower layer failure or a NAS signaling connection release). Fig.11 As shown, UE 1102 stops timer T3510 1128, terminates the initial registration process 1130, resets the corresponding registration attempt counter 1140, releases the NAS signaling connection locally 1150, and enters the PLMN search state 1160 to perform the SNPN selection process.

[0078] Fig.12 is an example diagram showing an example procedure of the UE during the initial registration process. Fig.12 As shown, in example procedure 1200, which is similar to example procedure 1000, UE 1202 (e.g., UE 701) sends an initial registration request 1210 to base station 1204 (e.g., gNB 722) to initiate an initial registration process for a selected SNPN. In particular, the selected SNPN is selected according to clause 4.9.3.1.1 a0) specified in 3GPP TS23.122 (i.e., the selected SNPN provides localized services for UE 1202). In addition, the initial registration request 1210 is not for emergency services and / or is not a process in which the PDU session initiation request type for emergency services is set to "existing emergency PDU session".

[0079] Once UE 1202 sends the initial registration request 1210, UE 1202 starts timer T3510 1220. Subsequently, the current tracking area identifier (TAI) may change. Specifically, TAI is an identifier used to identify a tracking area, which is a globally unique tracking area identifier consisting of a PLMNID and a TAC. When UE 1202 detects a change in TAI, UE 1202 determines that a first event has occurred (i.e., an abnormal situation has occurred). Optionally, UE 1202 may also determine whether a condition is met (e.g., localized service access in the selected SNPN is disabled; or the validity information of the selected SNPN is no longer met). If the first event occurs, and optionally the condition is met, UE 1202 may perform one or more operations 1225 (e.g., a change in TAI) in response to the first event. Fig.12 As shown, UE 1202 stops timer T3510 1228, aborts the initial registration process 1230, resets the corresponding registration attempt counter 1240, and enters the PLMN search state 1250 to perform the SNPN selection process.

[0080] It should be noted that in the example procedures 900, 1000, 1100 and 1200, several different examples of first events are provided (e.g., expiration of timer T3510, receipt of a registration reject message with an abnormal / unexpected cause value, receipt of a message from a lower layer indicating a lower layer failure or release of a NAS signaling connection, a change in TAI). Other examples of first events may include a failure to transmit a NAS message, and receipt of information from a lower layer indicating that an access attempt is prohibited.

[0081] Fig.13 is an example diagram showing an example procedure of UE in the mobility registration update process. Fig.13 As shown, in the example procedure 1300, UE 1302 (e.g., UE 701) sends a mobility registration update request 1310 to a base station 1304 (e.g., gNB722) to perform a mobility registration update procedure for a selected SNPN. In particular, the selected SNPN is selected according to clause 4.9.3.1.1 a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services for UE 902). In addition, the mobility registration update request 1310 is not a procedure for initiating an emergency PDU session.

[0082] Once UE 1302 sends the mobility registration update request 1310, UE 1302 starts timer T3510 1320. Fig.13As shown, if timer T3510 1320 times out 1325, an abnormal situation may occur. When timer T3510 1320 times out 1325, UE 1302 determines that a first event has occurred. Optionally, UE 1302 may also determine whether a condition is satisfied (e.g., localized service access in the selected SNPN is disabled; or the validity information of the selected SNPN is no longer satisfied). If the first event occurs, and optionally the condition is satisfied, UE 1302 may perform one or more operations in response to the first event (e.g., timer T3510 1320 times out 1325). As shown Fig.13 As shown, UE 1302 aborts the mobility registration update procedure 1330, resets the corresponding registration attempt counter 1340, and enters the PLMN search state 1350 to perform the SNPN selection procedure.

[0083] In the example process 1300, an example of a first event is provided (e.g., timeout of timer T3510). Other examples of the first event may include: receiving a registration reject message with an abnormal / unexpected cause value, receiving a message from a lower layer indicating a lower layer failure or a NAS signaling connection release, a change in TAI, a transmission failure of a NAS message, and receiving information from a lower layer indicating that an access attempt is prohibited.

[0084] Fig.14 is a diagram of an example process, showing the operation of the UE during the service request process. Fig.14 As shown, in the example process 1400, UE 1402 (e.g., UE 701) sends a service request 1410 to a base station 1404 (e.g., gNB 722) to perform a service request process for a selected SNPN. In particular, the selected SNPN is selected according to the selection specified in 3GPP TS23.122 Section 4.9.3.1.1 Clause a0) (i.e., the selected SNPN provides localized services for UE 902). In addition, the mobility registration update request 1410 is not used to initiate an emergency PDU session.

[0085] Once UE 1402 sends service request 1410, UE 1302 starts timer T3517 1420. Timer T3517 is a service request timer corresponding to the 5GMM service request procedure. Specifically, when UE 1402 sends a service request message, UE 1402 starts timer T3517 1420. In a normal stop situation, when UE 1402 receives a service accept message (indicating that the service request is accepted) or a service reject message (indicating that the service request is rejected) from the network (e.g., base station 1404), UE 1402 will stop timer T3517 1420. However, if Fig.14As shown, if timer T3517 1420 times out 1425, an abnormal situation may occur. When timer T3517 1420 times out 1425, UE 1402 determines that a first event has occurred. Optionally, UE 1402 may also determine whether a condition is satisfied (e.g., localized service access in the selected SNPN is disabled; or the validity information of the selected SNPN is no longer satisfied). If the first event occurs, and optionally the condition is satisfied, UE 1402 may perform one or more operations in response to the first event (e.g., timer T3517 1420 times out 1425). As shown Fig.14 As shown, UE 1402 terminates the service request process 1430, resets the corresponding service request attempt counter 1440, and enters the PLMN search state 1450 to perform the SNPN selection process.

[0086] In the example process 1400, an example of a first event is provided (e.g., timeout of timer T3517). Other examples of the first event may include: receiving a service rejection message with an abnormal / unexpected cause value, receiving a message from a lower layer indicating a lower layer failure or a NAS signaling connection release, a change in TAI, a transmission failure of a NAS message, and receiving information from a lower layer indicating that an access attempt is prohibited.

[0087] In certain configurations, in example processes 900-1400, when the UE performs an operation in response to the first event, the UE does not immediately restart the process.

[0088] Fig.15is a flowchart of an example process of a UE. The example process can be performed by a UE (e.g., UE 701). At operation 1510, the UE receives a DL NAS TRANSPORT message. At operation 1520, after receiving the DL NAS TRANSPORT message, the UE checks whether a second event has occurred. An example of a second event may include: the Payload container type IE is set to "N1 SM information" and the 5GMM cause IE is set to cause #74 "This SNPN is not authorized temporarily". Alternatively, at operation 1520, another example of a second event may include: the Payload container type IE is set to "N1 SM information" and the 5GMM cause IE is set to cause #75 "This SNPN is not authorized permanently". At operation 1530, in response to the second event, the UE performs one or more operations, including: delivering to the 5GSM sublayer an indication that the 5GSM message was not forwarded because this SNP N was temporarily / permanently not authorized (and the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message), setting the 5GS update status to 5U3 ROAMING NOT ALLOWED, deleting any 5G-GUTI, deleting the last visited registered TAI, deleting the TAI list, deleting the ngKSI, deleting the equivalent SN PN list (if any), storing the SNPN identity in a list of "temporarily prohibited SNPN" or "permanently prohibited SN PN" (for access to localized services in the SNPN, if the SNPN is selected according to 3GPPTS23.122 Section 4.9.3.1.1 clause a0)) for the specific access type for which the message was received, and entering state 5GMM-DEREGISTERED.PLMN-SEARCH and performing SNPN selection or SNPN selection for embarked services. If the message has successfully passed the integrity check of NAS, the UE sets the SNPN specific attempt counters for the 3GPP access and non-3GPP access of the current SNPN to the UE implementation specific maximum value. If the message has successfully passed the integrity check of NAS, and the UE also supports the registration procedure over other accesses of the same SNPN, the UE shall also process the 5GMM parameters and 5GMM status for that access as described by this 5GMM cause value.

[0089] Fig.16is a flowchart of an example process of a user equipment (UE). The example process can be performed by a UE (e.g., UE701). At operation 1610, the UE requests a process related to a PDU session. In some embodiments, the process can be a PDU session establishment process, a PDU session modification process, or a PDU session release process. At operation 1620, during the process related to the PDU session, the UE may encounter a third event in which an abnormal situation occurs. Examples of the third event may include, but are not limited to, receiving an indication that a 5GSM message was not forwarded because this SNPN was temporarily / permanently not authorized (together with a PDU session establishment / modification / release request message), and the PDU session ID IE is set to the same value as the PDU session ID sent by the UE. At operation 1630, in response to the third event, the UE performs one or more operations, including: stopping corresponding timers (e.g., timer T3580 during PDU session establishment, timer T3581 during PDU session modification, and timer T3582 during PDU session release), terminating processes related to the PDU session, locally releasing all non-emergency PDUs (locally releasing the PDU session during PDU session release), and not triggering a 5GSM process in the current SNPN unless the process is related to an emergency (until the UE deregisters from the SNPN).

[0090] Fig.17 is a flowchart of a method (process) for UE wireless communication. The method can be performed by the UE. At operation 1710, the UE starts a first 5GMM process on a first independent non-public network (SNPN) providing localized services. At operation 1720, in response to a first event, the UE performs one or more operations, including: terminating the first 5GMM process, resetting the corresponding process attempt counter of the first 5GMM process, stopping the corresponding timer of the first 5GMM process, if the NAS signaling connection exists, locally releasing the NAS signaling connection, and entering a PLMN search state to perform an SNPN selection process.

[0091] In some embodiments, the first event includes: localized service access in the first SNPN is no longer allowed for the UE.

[0092] In some embodiments, the first event includes satisfying a condition, and the condition is: localized service access in the first SNPN is disabled; or validity information of the first SNPN is no longer satisfied.

[0093] In some embodiments, the first event includes: timeout of the corresponding timer, receipt of a reject 5GMM message with an abnormal or unexpected cause value, receipt of information from a lower layer indicating a lower layer failure or release of the NAS signaling connection, a change in the current TAI, failure to transmit a NAS message, and receipt of information from a lower layer indicating that an access attempt is prohibited.

[0094] In some embodiments, in response to the first event, localized service access in the first SNPN is no longer allowed to the UE.

[0095] In some embodiments, the first 5GMM process is not a process for emergency services, nor is it a process for starting a PDU session for emergency services, and the request type is set to an existing emergency PDU session.

[0096] In some embodiments, the first 5GMM process is an initial registration process or a mobility registration update process. The corresponding process attempt counter is a registration attempt counter, and the corresponding timer is a registration timer (e.g., timer T3510).

[0097] In some embodiments, the first 5GMM process is a service request process. The corresponding process attempt counter is a service request attempt counter, and the corresponding timer is a service request timer (eg, timer T3517).

[0098] It is understood that the specific order or hierarchy in the disclosed process / flowchart is an illustration of an exemplary method. Based on design preferences, it is understood that the specific order or hierarchy in the process / flowchart can be rearranged. In addition, some blocks can be combined or omitted. The accompanying method claims show example orders of elements of various blocks and are not meant to be limited to the specific order or hierarchy shown.

[0099] The foregoing description is provided to any technical personnel to enable them to practice the various aspects described herein. Various modifications to these aspects will be apparent to the technical personnel, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to be given their full scope in accordance with the language of the claims, wherein the reference to a single element does not mean "only one" unless otherwise specified, but "one or more". The term "exemplary" used herein means "as an example, instance or illustration". Any aspect described as "exemplary" is not necessarily interpreted as being superior to other aspects. Unless otherwise specified, the term "some" refers to one or more. 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, terms 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" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described herein, which are known or later known to the skilled person, are expressly incorporated herein by reference, and are intended to be included in the claims. In addition, nothing disclosed herein is intended to be disclosed, whether or not explicitly mentioned in the claims. The terms "module," "mechanism," "element," "device," and the like shall not replace the term "means." Therefore, no claim element shall be interpreted as a means plus function unless the element expressly uses the phrase "means for."

Claims

1. A wireless communication method for a user equipment UE, characterized in that: include: Initiating a first 5G mobility management 5GMM process, the first 5GMM process being performed on a first independent non-public network SNPN providing localized services; and In response to a first event, performing one or more operations, including: Aborting the first 5GMM process, resetting a corresponding process attempt counter of the first 5GMM process, stopping a corresponding timer of the first 5GMM process, If there is a non-access stratum NAS signaling connection, the NAS signaling connection is released locally, and Entering a public land mobile network PLMN search state to perform a SNPN selection process.

2. The method according to claim 1, characterized in that The first event includes: Localized service access in the first SNPN is no longer allowed for the UE.

3. The method according to claim 1, characterized in that The first event includes satisfying a condition, and the condition is: Localised service access in the first SNPN is disabled; or The validity information of the first SNPN is no longer satisfied.

4. The method according to claim 1, characterized in that The first event includes: The corresponding timer expires, A reject 5GMM message with an abnormal or unexpected cause value is received, Receiving information indicating a failure or release of the NAS signalling connection, The current tracking area identifier TAI changes. Failure in the transmission of NAS messages, and A message is received indicating that the access attempt is prohibited.

5. The method according to claim 1, characterized in that The first 5GMM process is not an emergency service process, nor is it a start-up process for a packet data unit PDU session for emergency service, and the request type of the start-up process is set to an existing emergency PDU session.

6. The method according to claim 1, characterized in that The first 5GMM process is an initial registration process or a mobility registration update process.

7. The method according to claim 6, characterized in that The corresponding process attempt counter is a registration attempt counter, and the corresponding timer is a registration timer T3510.

8. The method according to claim 1, characterized in that The first 5GMM process is a service request process, the corresponding process attempt counter is a service request attempt counter, and the corresponding timer is a service request timer T3517.

9. The method according to claim 1, characterized in that The PLMN search state is 5GMM-REGISTERED.PLMN-SEARCH state or 5GMM-DEREGISTERED.PLMN-SEARCH state.

10. A device for wireless communication, characterized in that: The device is a user equipment UE, comprising: a memory; and At least one is coupled to the memory and configured to: Initiating a first 5G mobility management 5GMM process on a first independent non-public network SNPN providing localized services; and In response to a first event, performing one or more operations, including: Aborting the first 5GMM process, Resetting the corresponding process attempt counter of the first 5GMM process, Stop the corresponding timer of the first 5GMM process, If the non-access stratum NAS signaling connection exists, the NAS signaling connection is released locally, and Enter the public land mobile network PLMN search state to perform the SNPN selection process.