Processing of restricted service area cause in unrestricted case

Abstract

In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus can be a user equipment (UE). The UE receives a service reject message from a network. The service reject message includes a 5th generation mobility management (5GMM) cause value indicating a restricted service area. The UE determines that the service reject message is received via a non-3rd generation partnership project (3GPP) access other than a wired access. In response to the determining operation, the UE performs at least one action. The UE can enter a 5GMM-registered state. The UE can abort a service request procedure. The UE can stop a timer associated with the service request procedure. The UE can locally release resources allocated for the service request procedure.

Description

[0001] Cross-references

[0002] This application claims priority to Indian Patent Application No. 202421027388, filed on April 2, 2024, entitled “Handling of Reasons for Limited Service Areas in Unrestricted Circumstances”, the entire contents of which are hereby expressly incorporated by reference. Technical Field

[0003] This disclosure generally relates to wireless communications, and more specifically, to techniques for processing a “restricted service area” indication received by a user equipment (UE) in scenarios where the “restricted service area” indication is not applicable. Background Technology

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

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems 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.

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

[0007] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not an exhaustive summary of all hypothetical aspects, nor is it intended to identify key or important elements of all aspects, nor to depict 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 an introduction to the more detailed descriptions that follow.

[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. The UE receives a service rejection message from a network. The service rejection message includes a 5G Mobility Management (5GMM) reason value indicating a restricted service area. The UE determines that the service rejection message was received via a non-3GPP access other than wired access. In response to the above determination, the UE performs at least one action. The UE may enter a 5GMM-registered state. The UE may abort a service request procedure. The UE may stop a timer associated with the service request procedure. The UE may locally release resources allocated for the service request procedure.

[0009] To achieve the foregoing and related objectives, the one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of the one or more aspects are set forth in detail in the following description and drawings. However, these features indicate only a few of the many ways in which the principles of the aspects can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

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

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

[0012] Figure 3 This illustrates an example logical architecture for a distributed access network.

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

[0014] Figure 5 This is a schematic diagram illustrating a communication system that includes various access networks and devices for accessing the core network.

[0015] Figure 6 This is a flowchart of a wireless communication method. Detailed Implementation

[0016] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations, and not as representing the only configuration in which the concepts described herein can be practiced. This detailed description includes specific details used to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0017] Several aspects of a telecommunications system will now be presented with reference to various devices and methods. These devices and methods will be described in detail below and illustrated in the accompanying drawings by various program blocks, components, circuits, programs, algorithms, etc. (collectively, “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 on the specific application and the design constraints imposed on the system as a whole.

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

[0019] Therefore, in one or more example aspects, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the foregoing types, or any other medium capable of storing computer-executable code in the form of computer-accessible instructions or data structures.

[0020] Figure 1This is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base station 102, UE 104, Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a fifth-generation core network (5G Core, 5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macro cell includes a base station. The small cell includes nanocells, picocells, and microcells.

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

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

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

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

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

[0026] Base station 102 (whether it's a small cell 102' or a large-area (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations (e.g., gNB 180) may operate in conventional sub-6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or in near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Extremely high frequency (EHF) is a radio frequency segment of the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-millimeter waves can extend down to frequencies up to 3 GHz with wavelengths of 100 mm. The ultra-high frequency (SHF) band extends between 3 GHz and 30 GHz and is also known as centimeter waves. Communication using millimeter-wave / near-millimeter-wave radio frequency bands (e.g., 3 GHz to 300 GHz) has extremely high path loss and short range. Millimeter-wave base station 180 can work with UE 104 to utilize beamforming 182 to compensate for this extremely high path loss and short range.

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

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

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

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

[0031] Although this disclosure may refer to 5G new radio (NR), it may be applied to other similar fields, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM), or other radio / wireless access technologies.

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

[0033] The transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions associated with various signal processing functions. Layer 1 (including the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) encoding / decoding on the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 216 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The encoded, decoded, and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. This OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from channel estimator 274 can be used to determine the coding and modulation schemes and for spatial processing. These channel estimates can be derived from the reference signal transmitted by UE 250 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 220 via a separate transmitter 218TX. Each transmitter 218TX can modulate an RF carrier with the corresponding spatial stream for transmission.

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

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

[0036] Similar to the functions described in the DL transmission combined with base station 210, controller / processor 259 provides: RRC layer functions associated with the acquisition of system information (e.g., MIB, SIB), 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 the transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; 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 via HARQ, priority processing, and logical channel priority ordering.

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

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

[0039] NR can refer to a radio configured to operate under a new air interface (e.g., an air interface other than one based on Orthogonal Frequency Divisional Multiple Access (OFDMA)) or a fixed transport layer (e.g., a fixed transport layer other than IP). NR can utilize OFDM with a cyclic prefix (CP) on both the uplink and downlink, and can include support for half-duplex operation using time division duplexing (TDD). NR can include mission-critical applications for enhanced mobile broadband (eMBB) services with wide bandwidths (e.g., above 80 MHz), millimeter wave (mmW) services with high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) services with non-backward-compatible MTC technologies, and / or ultra-reliable low latency communications (URLLC) services.

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

[0041] The NR RAN can include a central unit (CU) and a distributed unit (DU). An NR base station (BS) (e.g., gNB, 5G Node B, Node B, TRP, AP) can correspond to one or more 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 a distributed unit) can configure these cells. A DCell can be a cell used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or handover. In some cases, a DCell may not transmit a synchronization signal (SS); in others, it may transmit an SS. An NR BS can transmit a downlink signal indicating the cell type to the UE. Based on this cell type indication, the UE can communicate with the NR BS. For example, the UE can determine which NR BS to consider for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0042] Figure 3 An example logical architecture of a distributed RAN 300 according to aspects of this disclosure is shown. A 5G access node 306 may include an access node controller (ANC) 302. This ANC may be the CU of the distributed RAN. The backhaul interface to the next-generation core network (NG-CN) 304 may terminate at this ANC. The backhaul interface to the adjacent next-generation access node (NG-AN) 310 may terminate at this ANC. This ANC may include one or more TRPs 308 (which may also be referred to as BS, NR BS, NodeB, 5G NB, AP, or some other terminology). As described above, TRP can be used interchangeably with "cell".

[0043] TRP 308 may be a DU. These TRPs may be connected to one ANC (ANC 302) or more ANCs (not shown). 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. TRPs may include one or more antenna ports. These TRPs may be configured to serve traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

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

[0045] This architecture enables collaboration between and within TRPs 308. For example, collaboration can be pre-configured within a TRP and / or across TRPs via ANC 302. Depending on the circumstances, inter-TRP interfaces may be unnecessary or nonexistent.

[0046] Depending on various factors, the distributed RAN 300 architecture allows for dynamic configuration of segmentation logic functions. PDCP, RLC, and MAC protocols can be adaptively placed at the ANC or TRP.

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

[0048] Figure 5 This is a schematic diagram 500 illustrating a communication system that includes various access networks and devices for accessing a 5G Core Network (5GCN) 550. In this example, UE 504 can connect to the 5GCN 550 via base station 502 in a PLMN or via base station 506 in a Stand-alone Non-Public Network (SNPN). Both base station 502 in the PLMN and base station 506 in the SNPN are connected to the 5GCN 550.

[0049] Additionally, UE 504 can access 5GCN 550 via non-3GPP access point 522. Non-3GPP access point 522 communicates with 5GCN 550. Furthermore, 5G residential gateway (5G-RG) 512 and fixed network residential gateway (FN-RG) 514 communicate with 5GCN 550 via Wireline Access Gateway Function (W-AGF) 518. 5G-RG 512 and FN-RG 514 communicate with W-AGF 518 connected to 5GCN 550. Computing device 505 or UE 504 can access 5GCN 550 via 5G-RG 512 or FN-RG 514. 5GCN 550 also includes AMF 560 among other components.

[0050] As part of the 5GCN 550, the AMF 560 can determine whether a UE, such as UE 504, is in an allowed or unallowed area. If the AMF 560 determines that UE 504 is in an unallowed area, and if the information element (IE) in the SERVICE REQUEST message sent by UE 504 is set to "signaling" or "data," the AMF 560 sends a SERVICE REJECT message to UE 504 with the 5GMM reason value set to #28, which indicates "restricted service area." However, if the service element (IE) in the SERVICE REQUEST message is set to "mobile terminal service," "emergency service," "emergency service fallback," "high priority access," or "high priority signaling," the AMF 560 continues to process the request unless there is another reason preventing acceptance.

[0051] Service area restrictions typically apply only to 3GPP access and wired access. When a UE such as UE 504 accesses 5GCN 550 via 3GPP access, or when a 5G-RG 512 or a W-AGF 518 representing an FN-RG 514 (or representing an N5GC device) accesses 5GCN 550 via wired access, reason value #28 indicates that the UE is in a restricted service area. In such cases, the UE enters the 5GMM-REGISTERED.NON-ALLOWED-SERVICE state, awaiting the release of the N1 NAS signaling connection and initiating the registration procedure.

[0052] In the first scheme, a potential problem arises when the UE receives the 5GMM cause value #28 from other types of access networks (e.g., non-3GPP access via non-3GPP access point 522) or from the SNPN via base station 506. In these scenarios, according to the first scheme, the UE's behavior is undefined, leading to ambiguity in the response. Specifically, it has been determined that the first scheme defines the UE's behavior in response to receiving the 5GMM cause value #28 indicating a "restricted service area" when the UE receives such a message via wired or 3GPP access. However, when the UE receives the 5GMM cause value #28 via non-3GPP access or via the SNPN, the UE's behavior is undefined and ambiguous. Therefore, a potential problem arises, for example, when UE 504 attempts to access 5GCN 550 via non-3GPP access point 522 or via the SNPN via base station 506 and receives the 5GMM cause value #28 ("restricted service area").

[0053] To resolve this ambiguity, in the second scheme, the UE operates according to the following rules: When a #28 is received from a cell belonging to a non-3GPP access and / or SNPN and / or from a 5G access network other than a wired access network, and a 5GMM reason #28 is received by a W-AGF representing an FN-CRG or FN-BRG, the UE shall perform one or more of the following actions: - Enter 5GMM - Registered status and / or - Suspend the service request process and / or - Stop timer T3517 and / or - Locally release any resources allocated to the service requester.

[0054] In other words, this second approach considers non-3GPP access (excluding wired access) or cause #28 received from SNPN as an anomalous situation. In this second approach, UE 504 considers receiving cause #28 via non-3GPP access or SNPN access as a trigger to enter a state consistent with anomalous situation handling. Once UE 504 determines this is an anomalous situation, it can enter the 5GMM-Registered state, abort any ongoing service request procedures, stop timer T3517 if it is running, and locally release the resources allocated for the service request procedure.

[0055] By defining these steps for receiving cause #28 outside its intended 3GPP or wired access range, UE 504 is no longer in an undefined state. Instead, it uses a predictable fallback procedure. This fallback classifies cause #28 as one of the listed anomalous causes, as described in the standard's handling of unexpected 5GMM cause values. As a result, UE 504 transitions to 5GMM-registered, aborts the attempt to complete the service request, and releases any temporarily reserved resources. This behavior allows UE 504 to avoid unintended restricted states, since the presence of cause #28 in the context of non-3GPP or SNPN access does not indicate a valid service area restriction in these deployments.

[0056] Under this approach, the overall protocol flow remains consistent with the normal service request logic defined for 5GMM. UE 504, accessing 5GCN 550 via base station 502 in the PLMN or the wired access network, follows existing 3GPP behavior when reason #28 is appropriately applied to 3GPP or wired service area restrictions. However, if reason #28 is sent under non-3GPP or SNPN circumstances, UE 504 has a well-defined fallback. Normal operation can resume without leaving UE 504 in an undefined state. This definition clarifies the handling of 5GMM state transitions and timer T3517, thereby preventing program loops or deadlocks when restricted service area reasons are used in ways not intended by the specification.

[0057] Service area restriction features in 5G systems are specifically designed for 3GPP access and wired access scenarios. Specific service area restrictions can be implemented when a UE accesses the 5GCN via 3GPP access, or when a 5G-RG or a W-AGF representing a Fixed Network Cable Residential Gateway (FN-CRG) (or an N5GC device) accesses the 5GCN via wired access. That is, the treatment of 5GMM cause #28 follows normal service area restriction processing in two specific scenarios: when the UE accesses the 5GCN via 3GPP access, or when a 5G-RG 512 or a W-AGF 518 representing an FN-CRG accesses the 5GCN via wired access. In these cases, the receiving entity enters the 5GMM-Registered.Unpermitted Service state and follows the standard service area restriction procedures.

[0058] 5GMM cause #28 indicates "Restricted Service Area," and its handling requires different treatment based on the access type through which the cause value was received. It is considered an anomalous case when the cause value is received via a non-3GPP access channel other than wired access, or when it is received by a W-AGF representing a Fixed Network Broadband Residential Gateway (FN-BRG). This treatment differs from the standard handling applied when the same cause value is received via 3GPP access or wired access channels (5G-RG, FN-CRG, N5GC devices).

[0059] As described above, in this exceptional scenario, UE 504 follows a specific set of actions. UE 504 enters the 5GMM-Registered state, aborts any ongoing service request procedures, stops timer T3517 if it is running, and locally releases any resources allocated to the service request procedure. This behavior provides a clear and definite response when the restricted service area indication is received in a context where it should not normally occur.

[0060] By defining this behavior, the system maintains consistent handling of service area restrictions where they are expected to apply, while providing clear procedures for situations where the restriction indication appears in unexpected contexts. This second approach helps prevent undefined states and maintain network connectivity stability, particularly when the UE 504 or other devices attempt to access the 5GCN 550 via various access types.

[0061] More specifically, when UE 504 receives 5GMM cause value #28 via non-3GPP access (excluding wired access) or via SNPN, UE 504 enters the 5GMM-Registered state. This action allows UE 504 to maintain a basic registration level with the network, even if the service request that triggered the cause value is not fully processed. Entering the 5GMM-Registered state enables UE 504 to maintain connectivity with the network and prepare for further actions, such as new registration procedures if necessary.

[0062] If a service request procedure is in progress when the 5GMM cause value #28 is received, UE 504 aborts the service request procedure. This service request procedure is initiated when UE 504 attempts to establish a connection for service. By aborting the procedure, UE 504 ceases any further attempts to establish the connection based on this initial request, thereby preventing potential loops or conflicts that could arise from continuing the procedure. Aborting the service request also avoids unnecessary signaling and resource usage.

[0063] UE 504 also stops timer T3517 while it is running. Timer T3517 is used in the service request procedure to manage the timing of requests and responses between UE 504 and the network. When the service request is rejected with a 5GMM reason value, such as being rejected with #28 in an exceptional case, UE 504 stops timer T3517. By stopping this timer, UE 504 avoids waiting for a response that will not arrive due to reason #28, which frees up resources and allows UE 504 to initiate other procedures as needed.

[0064] UE 504 then locally releases any resources allocated to the aborted service request procedure. When UE 504 initiates a service request, various resources (such as memory buffers, processing allocations, and signaling channels) can be reserved. By releasing these resources, UE 504 frees up capacity and reduces the likelihood of resource exhaustion. This step is important for maintaining the operational efficiency of UE 504 and the entire network.

[0065] In the third scheme, the UE operates according to the following rules: When 5GMM reason #28 is received except in the following circumstances: - When the UE accesses the 5GCN via 3GPP access; and / or - When the 5G-RG and / or the W-AGF representing the FN-CRG (or representing the N5GC device) access the 5GCN via wired access.

[0066] The UE should then perform one or more of the following actions: - Enter 5GMM - Registered status and / or - Suspend the service request process and / or - Stop timer T3517 and / or - Locally release any resources allocated to the service requester.

[0067] In this example, when UE 504 receives 5GMM reason #28 from an access network other than 3GPP access or wired access, the processing can be described as the reason value not being the intended applicable access type. Specifically, this includes scenarios where UE 504 receives the reason value from a non-3GPP access point 522 or from a base station 506 in an SNPN. This approach provides clarity by explicitly defining the situations in which standard service area restriction behavior should not apply.

[0068] This third approach recognizes that service area restrictions are specifically designed for 3GPP access and wired access scenarios. When UE 504 accesses 5GCN 550 via 3GPP access through base station 502, or when 5G-RG 512 or W-AGF 518 representing FN-CRG accesses 5GCN 550 via wired access, the normal service area restriction procedure applies. However, for all other access scenarios, UE 504 requires different handling.

[0069] Under this scheme, when UE 504 receives reason #28 outside of these expected contexts, it performs a series of well-defined actions. UE 504 transitions to the 5GMM-Registered state, maintaining its basic network registration. Subsequently, it suspends any ongoing service request procedures, as continuing such procedures would be inappropriate given the invalid context of the restriction indication. UE 504 also stops timer T3517 if it is running, thereby preventing unnecessary waiting periods associated with the service request procedure. Finally, UE 504 locally releases any resources allocated for the service request procedure, thus maintaining effective resource utilization.

[0070] Figure 6 This is a flowchart 600 of a wireless communication method. This method can be performed by a UE (e.g., UE 504). In operation 602, the UE receives a service rejection message from the network, the service rejection message including a 5GMM cause value indicating a restricted service area. In some configurations, the 5GMM cause value is #28. In operation 604, the UE determines that the service rejection message was received via a non-3GPP access other than wired access. In some configurations, the non-3GPP access includes access via a non-3GPP access point.

[0071] In operation 606, in response to determining that the service rejection message was received via a non-3GPP access other than wired access, the UE performs at least one of the following actions: enters the 5GMM-Registered state; aborts the service request procedure; stops the timer associated with the service request procedure; and locally releases the resources allocated for the service request procedure. In some configurations, after entering the 5GMM-Registered state, the UE maintains network registration while ceasing attempts to establish a connection based on the service request procedure. In some configurations, to locally release resources, the UE releases memory buffers, processing allocations, or signaling channels reserved for the service request procedure. In some configurations, to abort the service request procedure, the UE stops further attempts to establish a connection based on the service request procedure.

[0072] In some configurations, the UE determines that the service rejection message was received from the SNPN before performing the at least one action. In some configurations, the service request procedure is initiated by sending a service request message to the network.

[0073] In some configurations, before performing the at least one action, the UE determines that the service rejection message was received from an access network other than: a 3GPP access network; and a wired access network accessed by a fifth-generation residential gateway or a wired access gateway function representing a fixed-network cable residential gateway. In some configurations, before performing the at least one action, the UE determines that the service rejection message was received by a wired access gateway function representing a fixed-network broadband residential gateway. In some configurations, the UE initiates a new registration procedure after performing the at least one action.

[0074] It should be understood that the specific order or hierarchy of program blocks in the disclosed program / flowchart is an illustration of exemplary methods. Based on design preferences, it should be understood that the specific order or hierarchy of program blocks in this program / flowchart can be rearranged. Furthermore, some program blocks can be combined or omitted. The appended method claims present the elements of the various program blocks in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0075] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims, wherein references to elements in the singular form are not intended to mean “one and only one”, but rather “one or more” unless expressly stated otherwise. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or overriding other aspects. Unless expressly 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 multiple A, multiple B, or multiple 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" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure, whether now known to those skilled in the art or hereafter learned, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms "module," "mechanism," "element," "device," etc., do not replace the term "means." Therefore, unless an element is expressly recited using the phrase "means for…", no claim element should be construed as means plus function.

Claims

1. A wireless communication method performed by a user equipment, comprising: Receive a service denial message from the network, which includes a fifth-generation mobility management reason value indicating a restricted service area; as well as In response to determining that the service rejection message was received via a non-3rd generation partner program access other than wired access, perform at least one of the following actions: Entered fifth-generation mobility management - registered status; Abort the service request process; Stop the timer associated with the service requester; and Release the resources allocated to the service requester locally.

2. The method of claim 1, wherein the fifth-generation mobility management reason value is #28.

3. The method of claim 1, wherein the non-third generation partner program access includes access via a non-third generation partner program access point.

4. The method of claim 1, further comprising: Before performing any of these actions, it is determined that the service rejection message was received from an independent, non-public network.

5. The method of claim 1, wherein the service request procedure is initiated by sending a service request message to the network.

6. The method of claim 1, further comprising: Before performing any of these actions, it is determined that the service rejection message was received from an access network other than the following: The third-generation partner program will be integrated into the network; as well as A wired access network accessed by a fifth-generation residential gateway or a wired access gateway function representing a fixed network cable residential gateway.

7. The method of claim 1, further comprising: Before performing any of these actions, it is determined that the service rejection message was received by a wired access gateway function representing a fixed network broadband residential gateway.

8. The method of claim 1, wherein entering the fifth-generation mobility management-registered state includes maintaining network registration while ceasing attempts to establish a connection based on the service request procedure.

9. The method of claim 1, wherein the locally released resources include releasing memory buffers, processing allocations, or signaling channels reserved for the service requesting program.

10. The method of claim 1, wherein terminating the service request procedure includes stopping further attempts to establish a connection based on the service request procedure.

11. The method of claim 1, further comprising: A new registration process is initiated after performing at least one of these actions.

12. An apparatus for wireless communication, the apparatus being a user equipment, comprising: Memory; as well as At least one processor, coupled to the memory and configured as follows: Receive a service denial message from the network, which includes a fifth-generation mobility management reason value indicating a restricted service area; as well as In response to determining that the service rejection message was received via a non-3rd generation partner program access other than wired access, perform at least one of the following actions: Entered fifth-generation mobility management - registered status; Abort the service request process; Stop the timer associated with the service requester; and Release the resources allocated to the service requester locally.

13. The apparatus of claim 12, wherein the fifth-generation mobility management reason value is #28.

14. The apparatus of claim 12, wherein the non-third generation partner program access includes access via a non-third generation partner program access point.

15. The apparatus of claim 12, wherein the at least one processor is further configured to: Before performing any of these actions, it is determined that the service rejection message was received from an independent, non-public network.

16. The apparatus of claim 12, wherein the service request procedure is initiated by sending a service request message to the network.

17. The apparatus of claim 12, wherein the at least one processor is further configured to: Before performing any of these actions, it is determined that the service rejection message was received from an access network other than the following: The third-generation partner program will access the network; and A wired access network accessed by a fifth-generation residential gateway or a wired access gateway function representing a fixed network cable residential gateway.

18. The apparatus of claim 12, wherein the at least one processor is further configured to: Before performing any of these actions, it is determined that the service rejection message was received by a wired access gateway function representing a fixed network broadband residential gateway.

19. The apparatus of claim 12, wherein entering the fifth-generation mobility management-registered state includes maintaining network registration while ceasing attempts to establish a connection based on the service request procedure.

20. A computer-readable medium storing computer-executable code for wireless communication of a user equipment, including code for performing the following operations: Receive a service denial message from the network, which includes a fifth-generation mobility management reason value indicating a restricted service area; and In response to determining that the service rejection message was received via a non-3rd generation partner program access other than wired access, perform at least one of the following actions: Entered fifth-generation mobility management - registered status; Abort the service request process; Stop the timer associated with the service requester; and Release the resources allocated to the service requester locally.

Images