METHOD FOR HANDLING REGISTRATION AND SERVICE REQUEST PROCEDURES FOR LOCALIZED SERVICE CHANGE BETWEEN MET AND NOT MET

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefits of Indian Provisional Application No. 202321038858, entitled “A METHOD FOR HANDLING FOR LOCALIZED SERVICE CHANGE BETWEEN MET AND NOT MET” and filed on Jun. 6, 2023, which is expressly incorporated by reference herein in their entirety.

BACKGROUND
Field

The present disclosure relates generally to communication systems, and more particularly, to techniques of methods and apparatuses for handling for localized service change between met and not met.

Background

The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

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, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor 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 the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The method may be performed by a UE. In certain configurations, the UE initiates a first 5G mobility management (5GMM) procedure over a first standalone non-public network (SNPN). In response to a first event, the UE performs one or more actions, including: aborting the first 5GMM procedure, resetting a corresponding procedure attempt counter for the first 5GMM procedure, stopping a corresponding timer for the first 5GMM procedure, releasing locally a non-access stratum (NAS) signaling connection if the NAS signaling connection exists, and entering a public land mobile network (PLMN) search state to perform a SNPN selection procedure.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2 is a diagram illustrating a base station in communication with a UE in an access network.

FIG. 3 illustrates an example logical architecture of a distributed access network.

FIG. 4 illustrates an example physical architecture of a distributed access network.

FIG. 5 is a diagram showing an example of a DL-centric slot.

FIG. 6 is a diagram showing an example of an UL-centric slot.

FIG. 7 is a diagram illustrating a communication system having a PLMN, a SNPN and a PNO-NPN/CAG providing access for localized services.

FIG. 8 is a flow chart of an example procedure of a UE.

FIG. 9 is a diagram illustrating an example procedure of a UE in an initial registration procedure.

FIG. 10 is a diagram illustrating an example procedure of a UE in an initial registration procedure.

FIG. 11 is a diagram illustrating an example procedure of a UE in an initial registration procedure.

FIG. 12 is a diagram illustrating an example procedure of a UE in an initial registration procedure.

FIG. 13 is a diagram illustrating an example procedure of a UE in a mobility registration update procedure.

FIG. 14 is a diagram illustrating an example procedure of a UE in a service request procedure.

FIG. 15 is a flow chart of an example procedure of a UE.

FIG. 16 is a flow chart of an example procedure of a UE.

FIG. 17 is a flow chart of a method (process) for wireless communication of a UE.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes 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 (SoC), 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 functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example aspects, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through backhaul links 132 (e.g., SI interface). The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over backhaul links 134 (e.g., X2 interface). The backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102′ may have a coverage area 110′ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

Certain UEs 104 may communicate with each other using 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 through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102′ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

A base station 102, whether a small cell 102′ or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band (e.g., 3 GHz-300 GHz) has extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 108a. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal 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 each of the base station 180/UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The 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 be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as 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), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate 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 the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

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 be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the SMF 194 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.

The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Although the present disclosure may reference 5G New Radio (NR), the present disclosure may be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM), or other wireless/radio access technologies.

FIG. 2 is a block diagram of a base station 210 in communication with a UE 250 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 275. The controller/processor 275 implements layer 3 and layer 2 functionality. 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 medium access control (MAC) layer. The controller/processor 275 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, 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 functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 216 handles 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 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 produce multiple spatial streams. Channel estimates from a channel estimator 274 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the 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 respective spatial stream for transmission.

At the UE 250, each receiver 254RX receives a signal through its respective antenna 252. Each receiver 254RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams destined for the UE 250. If multiple spatial streams are destined for the UE 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. 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 comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were 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 functionality.

The controller/processor 259 can 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 UL, the controller/processor 259 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, 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 ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 210, the controller/processor 259 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a 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 the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antenna 252 via separate transmitters 254TX. Each transmitter 254TX may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station 210 in a manner similar to that described in connection with the receiver function at the UE 250. Each receiver 218RX receives a signal through its respective antenna 220. Each receiver 218RX recovers information modulated onto an RF carrier and provides the information to a RX processor 270.

The controller/processor 275 can 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 UL, the controller/processor 275 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 250. IP packets from the controller/processor 275 may be provided to the EPC 160. The controller/processor 275 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

New radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)). NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and may include support for half-duplex operation using time division duplexing (TDD). NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service.

A single component carrier bandwidth of 100 MHz may be supported. In one example, NR resource blocks (RBs) may span 12 sub-carriers with a sub-carrier bandwidth of 60 kHz over a 0.25 ms duration or a bandwidth of 30 kHz over a 0.5 ms duration (similarly, 50 MHz BW for 15 kHz SCS over a 1 ms duration). Each radio frame may consist of 10 subframes (10, 20, 40 or 80 NR slots) with a length of 10 ms. Each slot may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each slot may be dynamically switched. Each slot may include DL/UL data as well as DL/UL control data. UL and DL slots for NR may be as described in more detail below with respect to FIGS. 5 and 6.

The NR RAN may include a central unit (CU) and distributed units (DUs). A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity and may not 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 BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

FIG. 3 illustrates an example logical architecture of a distributed RAN 300, according to aspects of the present disclosure. 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 neighboring next generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with “cell.”

The TRPs 308 may be a distributed unit (DU). The TRPs may be connected to one ANC (ANC 302) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

The local architecture of the distributed RAN 300 may be used to illustrate fronthaul definition. The architecture may be defined that support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The architecture may share features and/or components with LTE. According to aspects, the next generation AN (NG-AN) 310 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.

The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 302. According to aspects, no inter-TRP interface may be needed/present.

According to aspects, a dynamic configuration of split logical functions may be present within the architecture of the distributed RAN 300. The PDCP, RLC, MAC protocol may be adaptably placed at the ANC or TRP.

FIG. 4 illustrates an example physical architecture of a distributed RAN 400, according to aspects of the present disclosure. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU may be centrally deployed. C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort 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 have distributed deployment. The C-RU may be closer to the network edge. A distributed unit (DU) 406 may host one or more TRPs. The DU may be located at edges of the network with radio frequency (RF) functionality.

FIG. 5 is a diagram 500 showing an example of a DL-centric slot. The DL-centric slot may include a control portion 502. The control portion 502 may exist in the initial or beginning portion of the DL-centric slot. The control portion 502 may include various scheduling information and/or control information corresponding to various portions of the DL-centric slot. In some configurations, the control portion 502 may be a physical DL control channel (PDCCH), as indicated in FIG. 5. The DL-centric 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 slot. The DL data portion 504 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE). In some configurations, the DL data portion 504 may be a physical DL shared channel (PDSCH).

The DL-centric slot may also include a common UL portion 506. The common UL portion 506 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion 506 may include feedback information corresponding to various other portions of the DL-centric slot. 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 ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion 506 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information.

As illustrated in FIG. 5, 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 may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

FIG. 6 is a diagram 600 showing an example of an UL-centric slot. The UL-centric slot may include a control portion 602. The control portion 602 may exist in the initial or beginning portion of the UL-centric slot. The control portion 602 in FIG. 6 may be similar to the control portion 502 described above with reference to FIG. 5. The UL-centric slot may also include an UL data portion 604. The UL data portion 604 may sometimes be referred to as the pay load of the UL-centric slot. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).

As illustrated in FIG. 6, the end of the control portion 602 may be separated in time from the beginning of the UL data portion 604. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centric slot may also include a common UL portion 606. The common UL portion 606 in FIG. 6 may be similar to the common UL portion 506 described above with reference to FIG. 5. The common UL portion 606 may additionally or alternatively include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

In some circumstances, 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 relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

A Public Land Mobile Network (PLMN) is a network established and operated by an administration or recognized operating agency (ROA) for the specific purpose of providing land mobile communication services to the public. PLMN provides communication possibilities for mobile users. A PLMN may provide service in one or a combination of frequency bands. Access to PLMN services is achieved by means of an air interface involving radio communications between mobile phones and base stations with integrated IP network services. One PLMN may include multiple radio access networks (RAN) utilizing different RATs for accessing mobile services. A radio access network is part of a mobile communication system, which implements a radio access technology. Conceptually, RAN resides between a mobile device and provides connection with its core network (CN). Depending on the standard, mobile phones and other wireless connected devices are varyingly known as user equipment (UE, i.e., MS), terminal equipment (TE), mobile stations (MS, i.e., UE), mobile termination (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 RAT including WiFi.

As compared to PLMN, a non-public network (NPN) is a network for non-public use. An NPN is either a Stand-alone Non-Public Network (SNPN), i.e., operated by an NPN operator and not relying on network functions provided by a PLMN; or a Public Network Integrated NPN (PNI-NPN), i.e., a non-public network deployed with the support of a PLMN. A Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder. The combination of a PLMN ID and Network identifier (NID) identifies an SNPN. A UE may be enabled for SNPN.

PNI-NPNs are NPNs made available via PLMNs e.g., by means of dedicated DNNs, or by one or more Network Slice instances allocated for the NPN. When a PNI-NPN is made available via a PLMN, then the UE shall have a subscription of the PLMN in order to access PNI-NPN. As network slicing does not enable the possibility to prevent UEs from trying to access the network in areas where the UE is not allowed to use the Network Slice allocated for the NPN, Closed Access Groups can be used to apply access control for PNI-NPN. A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). CAG is used for access control e.g., authorization at cell selection and configured in the subscription as part of the Mobility Restrictions. A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID.

Local or localized services are services that are localized (e.g., provided at specific/limited area and/or are bounded in time). A localized service provider is an application provider or a network operator who make their services localized and to be offered to end user via a hosting network. A hosting network is a network that provides (access for) Localized services, and a hosting network can be an SNPN or a PNI-NPN, while a home network is network owning the current in use subscription or credential of the UE. Home network can be either Home-PLMN or Subscribed-SNPN. End user can enable or disable to access localized services. If the end user disables to access Localized services, the UE (i.e., MS) may not access an NPN providing access for Localized services.

For providing access for localized services to UE, the UE needs to be able to discover, select and access an NPN (as a hosting network) providing access for localized services.

FIG. 7 is a diagram illustrating a communication system 700 having a PLMN 710, a SNPN 720, and a Public Network Integrated NPN (PNI-NPN)/CAG 730 providing access for Localized services. As shown in FIG. 7, the PLMN network 710 includes control plane functionalities, user plane functionality (e.g., UPF), and applications that provides various services by communicating with a plurality of user equipments (UEs) including UE 701. The serving base station (e.g., gNB) 712 belongs to part of a radio access network (RAN) 740. The RAN 740 provides radio access for UE 701 via a RAT. An access and mobility management function (AMF) in the PLMN 710 communicates with the gNB 712. The UE 701 may be equipped with a radio frequency (RF) transceiver or multiple RF transceivers.

The SNPN network 720 includes control plane functionalities, user plane functionality (e.g., UPF), and applications that provides various services by communicating with a plurality of UEs including the UE 701. The combination of a PLMN ID and Network identifier (NID) identifies an SNPN. A serving base station (e.g., gNB) 722 belongs to part of a RAN 750. The RAN 750 provides radio access for the UE 701 via a RAT. An 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 a public network. A Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the CH. NG-RAN nodes which provide access to SNPNs broadcast the following information: One or multiple PLMN IDs, and a List of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to (723). An SNPN-enabled UE is configured with PLMN ID and NID (SNPN ID) of the subscribed SNPN, and an SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder may additionally be configured with information for SNPN selection (SNPN selection information or configuration) and registration using the SNPN subscription or using PLMN subscription (USIM) (in SNPN access mode) (702).

The PNI-NPN (CAG) network 730 includes control plane functionalities (which is optional, as it may rely on PLMN's control plane functionality), user plane functionality (which is optional, as it may rely on PLMN's user plane functionality), and applications that provides various services by communicating with a plurality of UEs including the UE 701. The PNI-NPN (CAG) 730 is a non-public network deployed with the support of a PLMN, e.g., the PLMN 710, by sharing e.g., RAN/gNB 712 and e.g., control plane functionalities. The CAG identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. The CAG is used for the PNI-NPNs to prevent the UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID. A CAG cell broadcasts one or multiple CAG Identifiers per PLMN (113), and a UE is configured with CAG related configuration/information (e.g., an (enhanced) CAG information list containing list of allowed CAGs per PLMN) (702).

Local or localized services are services that are localized (i.e., provided at specific/limited area and/or are bounded in time (a specific period of time)). A localized service provider is an application provider or a network operator who makes their services localized and to be offered to end user via a hosting network. A hosting network is a network that provides access for localized services and can be an SNPN or a PNI-NPN, while a home network is network owning the current in use subscription or credential of the UE. In the example of FIG. 7, both the SNPN 720 and the PNI-NPN (CAG) 730 can be a hosting network providing access for Localized services to the UE 701.

When localized services in a network are completed, all UEs registered with the network are expected to be moved to other network or to other cells within the same network. The other network can be HPLMN, VPLMN or another SNPN. The UE can stop using the network resources for localized services for numerous reasons, e.g.: (a) localized services in a network are completed; (b) validity conditions of network selection information are no longer met; (c) the user decides to stop using the localized services before they are completed (e.g., end user disables to access Localized services); or (d) a policy decision is taken by the network, with the effect that the UE is deregistered before the localized services are completed. Validity information or restrictions or criteria or conditions (703) are provided or configured to the UE as part of the localized service information, which are used to restrict the UE's access of the SNPN/PNI-NPN (as hosting network) providing access for Localized services. For providing localized services to the UE, the UE needs to be able to discover, select and access a SNPN/PNI-NPN (as hosting network) providing access for the localized services. The discovery mechanism is based on provisioning or configuring the UE with appropriate information.

FIG. 8 is a flow chart of an example procedure of a UE. The example procedure may be performed by a UE (e.g., UE 701). At operation 810, the UE initiates a first 5GMM procedure over a first SNPN providing localized services. Specifically, the first SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the first SNPN provides localized services to the UE). In certain embodiments, the first 5GMM procedure may be an initial registration procedure or a mobility registration update procedure. Alternatively, the first 5GMM procedure may be a service request procedure. It should be noted that the first 5GMM procedure is not a procedure for emergency services and is not a procedure for initiating a packet data unit (PDU) session for emergency services with a request type set to existing emergency PDU session. At operation 820, during the first 5GMM procedure, the UE may encounter a first event, in which abnormal cases happen. When the first event occurs, access for the localized services in the first SNPN is no longer allowed for the UE. Examples of the first event may include, without being limited thereto, timeout of a corresponding timer, receiving a reject message with an abnormal or unexpected cause value, receiving information from lower layers indicating a lower layer failure or release of the NAS signaling connection, change in a current tracking area identity (TAI), transmission failure of a NAS message, and receiving information from lower layers indicating that an access attempt is barred. Optionally, the first event may include a condition being satisfied, and the condition is: access for the localized services in the first SNPN is disabled; or validity information for the first SNPN is no longer met. In response to the first event (i.e., abnormal cases happen), access for the localized services 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 actions, including: aborting the first registration procedure, resetting a corresponding procedure attempt counter for the first registration procedure, stopping a corresponding timer for the first registration procedure, releasing locally a non-access stratum (NAS) signaling connection if the NAS signaling connection exists, and entering a PLMN search state to perform a SNPN selection procedure. In certain embodiments, the UE may perform the one or more actions as soon as possible in response to the first event. Alternatively, in certain embodiments, the UE may perform the one or more actions later in response to the first event.

FIG. 9 is a diagram illustrating an example procedure of a UE in an initial registration procedure. As shown in FIG. 9, in the example procedure 900, the UE 902 (e.g., UE 701) transmits an initial registration request 910 to the base station 904 (e.g., gNB 722) for a selected SNPN to initial an initial registration procedure. In particular, the selected SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to the UE 902). Further, the initial registration request 910 is not for emergency services and/or not for initiating a PDU session for emergency services with request type set to “existing emergency PDU session.”

Once the UE 902 transmits the initial registration request 910, the UE 902 starts a timer T3510 920. The timer T3510 is a registration timer corresponding to the 5GMM registration procedure. Specifically, when the UE 902 transmits the REGISTRATION REQUEST message (e.g., the initial registration request 910), the UE 902 starts the timer T3510 920. In a normal stop case, the UE 902 will stop the timer T3510 920 when the UE receives, from the network (e.g., base station 904), the REGISTRATION ACCEPT message (indicating that the registration request is accepted) or the REGISTRATION REJECT message (indicating that the registration request is rejected). However, an abnormal case may happen if a timeout 925 of the timer T3510 920 occurs, as shown in FIG. 9.

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

FIG. 10 is a diagram illustrating an example procedure of a UE in an initial registration procedure. As shown in FIG. 10, in the example procedure 1000, which is similar to the example procedure 900, the UE 1002 (e.g., UE 701) transmits an initial registration request 1010 to the base station 1004 (e.g., gNB 722) for a selected SNPN to initial an initial registration procedure. In particular, the selected SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to the UE 1002). Further, the initial registration request 1010 is not for emergency services and/or not for initiating a PDU session for emergency services with request type set to “existing emergency PDU session.”

Once the UE 1002 transmits the initial registration request 1010, the UE 1002 starts a timer T3510 1020. 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 case happens. When the UE 1002 receives the registration reject message 1025 with the abnormal/unexpected cause value, the UE 1002 determines that a first event occurs. Optionally, the UE 1002 may also determine whether the condition is satisfied (e.g., access for the localized services in the selected SNPN is disabled; or validity information for the selected SNPN is no longer met). If the first event occurs, and optionally the condition is satisfied, the UE 1002 may perform one or more actions in response to the first event (e.g., receiving the registration reject message 1025 with the abnormal/unexpected cause value). As shown in FIG. 10, the UE 1002 stops the timer T3510 1028, aborts the initial registration procedure 1030, resets the corresponding registration attempt counter 1040, and enters a PLMN search state 1050 to perform a SNPN selection procedure.

FIG. 11 is a diagram illustrating an example procedure of a UE in an initial registration procedure. As shown in FIG. 11, in the example procedure 1100, which is similar to the example procedure 1000, the UE 1102 (e.g., UE 701) transmits an initial registration request 1110 to the base station 1104 (e.g., gNB 722) for a selected SNPN to initial an initial registration procedure. In particular, the selected SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to the UE 1102). Further, the initial registration request 1110 is not for emergency services and/or not for initiating a PDU session for emergency services with request type set to “existing emergency PDU session.” Moreover, the UE 1102 may be in a NAS signaling connection.

Once the UE 1102 transmits the initial registration request 1110, the UE 1102 starts a timer T3510 1120. Subsequently, the UE 1102 may receive a message from the lower layers indicating a lower layer failure or release of the NAS signaling connection. When the UE 1102 receives the message from the lower layers indicating the lower layer failure or release of the NAS signaling connection, the UE 1102 determines that a first event occurs (i.e., abnormal cases happen). Optionally, the UE 1102 may also determine whether the condition is satisfied (e.g., access for the localized services in the selected SNPN is disabled; or validity information for the selected SNPN is no longer met). If the first event occurs, and optionally the condition is satisfied, the UE 1102 may perform one or more actions in response to the first event (e.g., receiving the message from the lower layers indicating the lower layer failure or release of the NAS signaling connection). As shown in FIG. 11, the UE 1102 stops the timer T3510 1128, aborts the initial registration procedure 1130, resets the corresponding registration attempt counter 1140, locally releases the NAS signaling connection 1150, and enters a PLMN search state 1160 to perform a SNPN selection procedure.

FIG. 12 is a diagram illustrating an example procedure of a UE in an initial registration procedure. As shown in FIG. 12, in the example procedure 1200, which is similar to the example procedure 1000, the UE 1202 (e.g., UE 701) transmits an initial registration request 1210 to the base station 1204 (e.g., gNB 722) for a selected SNPN to initial an initial registration procedure. In particular, the selected SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to the UE 1202). Further, the initial registration request 1210 is not for emergency services and/or not for initiating a PDU session for emergency services with request type set to “existing emergency PDU session.”

Once the UE 1202 transmits the initial registration request 1210, the UE 1202 starts a timer T3510 1220. Subsequently, a change in a current tracking area identity (TAI) may occur. Specifically, the TAI is the identity used to identify tracking areas, which is a globally unique tracking area identifier made up of the PLMN ID and the TAC. When the UE 1202 detects the change in the TAI, the UE 1202 determines that a first event occurs (i.e., abnormal cases happen). Optionally, the UE 1202 may also determine whether the condition is satisfied (e.g., access for the localized services in the selected SNPN is disabled; or validity information for the selected SNPN is no longer met). If the first event occurs, and optionally the condition is satisfied, the UE 1202 may perform one or more actions in response to the first event (e.g., change in the TAI). As shown in FIG. 12, the UE 1202 stops the timer T3510 1228, aborts the initial registration procedure 1230, resets the corresponding registration attempt counter 1240, and enters a PLMN search state 1250 to perform a SNPN selection procedure.

It should be noted that, in the example procedures 900, 1000, 1100 and 1200, several different examples of the first event are provided (e.g., timeout of the timer T3510, receiving the registration reject message with the abnormal/unexpected cause value, receiving the message from the lower layers indicating the lower layer failure or release of the NAS signaling connection, change in the TAI). Other examples of the first event may include transmission failure of a NAS message, and receiving information from lower layers indicating that an access attempt is barred.

FIG. 13 is a diagram illustrating an example procedure of a UE in a mobility registration update procedure. As shown in FIG. 13, in the example procedure 1300, the UE 1302 (e.g., UE 701) transmits a mobility registration update request 1310 to the base station 1304 (e.g., gNB 722) for a selected SNPN to perform a mobility registration update procedure. In particular, the selected SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to the UE 902). Further, the mobility registration update request 1310 is not for initiating an emergency PDU session.

Once the UE 1302 transmits the mobility registration update request 1310, the UE 1302 starts a timer T3510 1320. However, an abnormal case may happen if a timeout 1325 of the timer T3510 1320 occurs, as shown in FIG. 13. When the timeout 1325 of the timer T3510 1320 occurs, the UE 1302 determines that a first event occurs. Optionally, the UE 1302 may also determine whether the condition is satisfied (e.g., access for the localized services in the selected SNPN is disabled; or validity information for the selected SNPN is no longer met). If the first event occurs, and optionally the condition is satisfied, the UE 1302 may perform one or more actions in response to the first event (e.g., the timeout 1325 of the timer T3510 1320). As shown in FIG. 13, the UE 1302 aborts the mobility registration update procedure 1330, resets the corresponding registration attempt counter 1340, and enters a PLMN search state 1350 to perform a SNPN selection procedure.

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

FIG. 14 is a diagram illustrating an example procedure of a UE in a service request procedure. As shown in FIG. 14, in the example procedure 1400, the UE 1402 (e.g., UE 701) transmits a service request 1410 to the base station 1404 (e.g., gNB 722) for a selected SNPN to perform a service request procedure. In particular, the selected SNPN was selected according to clause 4.9.3.1.1 bullet a0) specified in 3GPP TS 23.122 (i.e., the selected SNPN provides localized services to the UE 902). Further, the mobility registration update request 1410 is not for initiating an emergency PDU session.

Once the UE 1402 transmits the service request 1410, the UE 1302 starts a timer T3517 1420. The timer T3517 is a service request timer corresponding to the 5GMM service request procedure. Specifically, when the UE 1402 transmits the SERVICE REQUEST message, the UE 1402 starts the timer T3517 1420. In a normal stop case, the UE 1402 will stop the timer T3517 1420 when the UE receives, from the network (e.g., base station 1404), the SERVICE ACCEPT message (indicating that the service request is accepted) or the SERVICE REJECT message (indicating that the service request is rejected). However, an abnormal case may happen if timeout 1425 of the timer T3517 1420 occurs, as shown in FIG. 14. When the timeout 1425 of the timer T3517 1420 occurs, the UE 1402 determines that a first event occurs. Optionally, the UE 1402 may also determine whether the condition is satisfied (e.g., access for the localized services in the selected SNPN is disabled; or validity information for the selected SNPN is no longer met). If the first event occurs, and optionally the condition is satisfied, the UE 1402 may perform one or more actions in response to the first event (e.g., the timeout 1425 of the timer T3517 1420). As shown in FIG. 14, the UE 1402 aborts the service request procedure 1430, resets the corresponding service request attempt counter 1440, and enters a PLMN search state 1450 to perform a SNPN selection procedure.

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

In certain configurations, in the example procedures 900-1400, when the UE performs the actions in response to the first event, the UE does not re-initiate the procedure immediately.

FIG. 15 is a flow chart of an example procedure of a UE. The example procedure may be performed by a UE (e.g., UE 701). At operation 1510, the UE receives a DL NAS TRANSPORT message. At operation 1520, upon reception of the DL NAS TRANSPORT message, the UE checks whether a second event occurs. An example of the second event may include: the Payload container type IE is set to “N1 SM information,” and the 5GMM cause IE is set to the Cause #74 “Temporarily not authorized for this SNPN.” Alternatively, at operation 1520, another example of the second event may include: the Payload container type IE is set to “N1 SM information,” and the 5GMM cause IE is set to the Cause #75 “Permanently not authorized for this SNPN.” At operation 1530, in response to the second event, the UE performs one or more actions, including: passing to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to Temporarily/Permanently not authorized for this SNPN (along with 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 last visited registered TAI, deleting the TAI list, deleting ngKSI, deleting the list of equivalent SNPNs (if available), storing the SNPN identity in the “temporarily forbidden SNPNs” or “permanently forbidden SNPNs” (for access for localized services in SNPN, if the SNPN was selected according to 3GPP TS 23.122, clause 4.9.3.1.1 bullet a0)) list for the specific access type for which the message was received, and entering state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services. If the message has been successfully integrity checked by the NAS, the UE set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value.

FIG. 16 is a flow chart of an example procedure of a UE. The example procedure may be performed by a UE (e.g., UE 701). At operation 1610, the UE requests a PDU session related procedure. In certain embodiments, the procedure may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure. At operation 1620, during the PDU session related procedure, the UE may encounter a third event, in which abnormal cases happen. Examples of the third event may include, without being limited thereto, receiving an indication that the 5GSM message was not forwarded because Temporarily/Permanently not authorized for this SNPN ((along with a PDU SESSION ESTABLISHMENT/MODIFICATION/RELEASE REQUEST message), with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE. At operation 1630, in response to the third event, the UE performs one or more actions, including: stopping a corresponding timer (e.g., a timer T3580 in the case of the PDU session establishment procedure, a timer T3581 in the case of the PDU session modification procedure, and a timer T3582 in the case of the PDU session release procedure), aborting the PDU session related procedure, locally releasing all non-emergency PDU (and in the case of the PDU session release procedure, locally releasing the PDU session), and not triggering a 5GSM procedure except that procedure is related to emergency (until the UE is deregistered from the SNPN) in the current SNPN.

FIG. 17 is a flow chart of a method (process) for wireless communication of a UE. The method may be performed by a UE. At operation 1710, the UE initiates a first 5GMM procedure over a first SNPN providing localized services. At operation 1720, in response to a first event, the UE performs one or more actions, including: aborting the first 5GMM procedure, resetting a corresponding procedure attempt counter for the first 5GMM procedure, stopping a corresponding timer for the first 5GMM procedure, releasing locally a NAS signaling connection if the NAS signaling connection exists, and entering a PLMN search state to perform a SNPN selection procedure.

In certain embodiments, the first event includes: access for the localized services in the first SNPN is no longer allowed for the UE.

In certain embodiments, the first event includes a condition being satisfied, and the condition is: access for the localized services in the first SNPN is disabled; or validity information for the first SNPN is no longer met.

In certain embodiments, the first event includes: timeout of the corresponding timer for the 5GMM procedure, receiving a reject 5GMM message with an abnormal or unexpected cause value, receiving information from lower layers indicating a lower layer failure or release of the NAS signaling connection, change in a current TAI, transmission failure of a NAS message, and receiving information from lower layers indicating that an access attempt is barred.

In certain embodiments, in response to the first event, access for the localized services in the first SNPN is no longer allowed for the UE.

In certain embodiments, the first 5GMM procedure is not a procedure for emergency services and is not a procedure for initiating a PDU session for emergency services with a request type set to existing emergency PDU session.

In certain embodiments, the first 5GMM procedure is an initial registration procedure or a mobility registration update procedure. The corresponding procedure attempt counter is a registration attempt counter, and the corresponding timer is a registration timer (e.g., timer T3510).

In certain embodiments, the first 5GMM procedure is a service request procedure. The corresponding procedure attempt counter is a service request attempt counter, and the corresponding timer is a service request timer (e.g., timer T3517).

It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous 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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” The word “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 specifically stated otherwise, the term “some” refers to 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 multiples of A, multiples of B, or multiples of C. Specifically, 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” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

METHOD FOR HANDLING REGISTRATION AND SERVICE REQUEST PROCEDURES FOR LOCALIZED SERVICE CHANGE BETWEEN MET AND NOT MET

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

Priority Claims (1)