Techniques for negotiating user equipment capabilities to obtain a list of radio access technology restrictions from a network

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. The user equipment sends a capability indication to a network indicating support for a radio access technology restriction function. The user equipment receives a restricted radio access technology information list from the network after indicating support for the function. The user equipment applies the restricted radio access technology information list to cell selection and reselection for non-emergency services.

Description

[0001] Cross-referencing

[0002] This application claims priority to Indian Patent Application Serial No. 202421054409, entitled “Method for Negotiating the Ability to Obtain a RAT Restriction List from a Network”, filed on July 16, 2024, 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 negotiating control over the use of radio access technology (RAT) between a user equipment and a network, and to techniques for providing a list of RAT restrictions from the network to the user equipment based on the negotiated capabilities. Background Technology

[0004] The statements in this section provide only background information in relation to 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 various multi-user access technologies, supporting communication with multiple users by sharing available system resources. Examples of such multi-user 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 multi-user access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. One example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband driven by the Third Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT), and other needs). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are still needed. These improvements may also apply to other multi-user access technologies and the telecommunications standards that adopt them. Summary of the Invention

[0007] The following content presents one or more aspects in a simplified manner to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all hypothetical aspects, nor is it intended to identify key or essential elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present certain concepts of one or more aspects in a simplified form as a prelude to a more detailed description thereafter.

[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The UE sends a capability indication to a network, the capability indication indicating support for a radio access technology restriction function. After the UE indicates support for the function, it receives a list of restricted radio access technology information from the network. The UE applies this list of restricted radio access technology information to cell selection and reselection for non-emergency services.

[0009] In one aspect of this disclosure, a method, a computer-readable medium, and a network are provided. The network may include one or more network entities. The one or more network entities receive a capability indication from a user equipment (UE) indicating whether the UE supports a radio access technology restriction function. Based on the received capability indication, the one or more network entities determine whether to apply radio access technology usage control. When the UE indicates support for the radio access technology restriction function, the one or more network entities send a list of restricted radio access technologies to the UE.

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

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

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

[0013] Figure 3 Example of a distributed access network's logical architecture.

[0014] Figure 4 Example of a distributed access network physical architecture.

[0015] Figure 5 This is a schematic diagram of a wireless communication environment with multiple wireless access technologies, in which network operators may need to regulate the use of wireless access technologies.

[0016] Figure 6 A flowchart of a method for obtaining and applying a list of restrictions on wireless access technologies from a network.

[0017] Figure 7 A flowchart illustrating the methods used to manage wireless access technologies. Detailed Implementation

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

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

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

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

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

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

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

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

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

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

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

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

[0030] The Evolved Packet Core (EPC) 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between User Equipment 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides user equipment IP address allocation and other functions. PDN gateway 172 and BM-SC 170 connect to IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched Streaming Service (PS Streaming Service), and / or other IP services. BM-SC 170 provides functions for providing and delivering MBMS user services. BM-SC 170 can serve as an entry point for content provider MBMS transmissions, and can be used to authorize and initiate MBMS bearer services within the 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 station 102, which belongs to the Multicast Broadcast Single Frequency Network (MBSFN) area and broadcasts specific services, and is responsible for session management (start / stop) and collecting billing information related to enhanced MBMS (eMBMS).

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

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

[0033] Although this disclosure may relate to 5G New Radio (NR), it may also 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 wireless / wireless access technologies.

[0034] Figure 2This is a block diagram illustrating communication between a base station 210 and a user equipment 250 in an access network. In the downlink, IP packets from EPC 160 can be provided to the controller / processor 275. The controller / processor 275 implements Layer 3 and Layer 2 functions. Layer 3 includes the radio resource control (RRC) layer, and Layer 2 includes the packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, and medium access control (MAC) layer. The controller / processor 275 provides RRC layer functions related to system information (e.g., Master Information Block (MIB), System Information Block (SIB)) broadcasting, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of user equipment measurement reports; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to uplink 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 performs functions related to TB demultiplexing, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority-related MAC layer functions.

[0035] Transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions related to various signal processing functions. Layer 1 includes a physical (PHY) layer, which may include error detection of the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and multiple-input multiple-output (MIMO) antenna processing. TX processor 216 processes the mapping to the signal constellation according to various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an Orthogonal Frequency Division Multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 274 can be used to determine coding and modulation schemes, as well as spatial processing. The channel estimates can be derived from the reference signal and / or channel state feedback transmitted by user equipment 250. Each spatial stream can then be provided to different antennas 220 via a separate transmitter 218TX. Each transmitter 218TX can be transmitted using a corresponding spatial stream modulated on an RF carrier.

[0036] At user equipment 250, each receiver 254RX receives a signal via its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the radio frequency carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and RX processor 256 implement Layer 1 functions related to various signal processing functions. The RX processor 256 can perform spatial processing on the information to recover any spatial stream facing user equipment 250. If multiple spatial streams are facing user equipment 250, they can be merged into a single OFDM symbol stream by the RX processor 256. The RX processor 256 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each OFDM signal subcarrier. 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 initially transmitted by base station 210 on the physical channel. The data and control signals are then provided to controller / processor 259, which implements Layer 3 and Layer 2 functions.

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

[0038] Similar to the downlink transmission functions described in base station 210, controller / processor 259 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to uplink PDU transmission, 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 related to mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority.

[0039] The channel estimate derived by the channel estimator 258 from the reference signal or feedback sent by the base station 210 can be used by the TX processor 268 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 268 can be provided to different antennas 252 via individual transmitters 254TX. Each transmitter 254TX can be transmitted using the corresponding spatial stream modulated on an RF carrier. The uplink transmission is processed at the base station 210 in a manner similar to the description related to the receiver function of the user equipment 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 the information to the RX processor 270.

[0040] Controller / processor 275 may be associated with a memory 276 that stores program code and data. Memory 276 may be referred to as a computer-readable medium. In the uplink, controller / processor 275 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from user equipment 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.

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

[0042] It can support a single component carrier bandwidth of 100 MHz. In one example, NR resource blocks (RBs) can span 12 subcarriers with a subcarrier bandwidth of 60 kHz and a duration of 0.25 ms, or a bandwidth of 30 kHz and a duration of 0.5 ms (similarly, a 15 kHz subcarrier spacing (SCS) has a 50 MHz bandwidth over a 1 ms duration). Each radio frame can contain 10 subframes (10, 20, 40, or 80 NR slots) with a length of 10 ms. Each slot can indicate the link direction used for data transmission (i.e., downlink or uplink), and the link direction of each slot can be dynamically switched. Each slot can contain downlink / uplink data and downlink / uplink control data. See below for details on NR uplink and downlink slots. Figure 5 and Figure 6 A detailed description.

[0043] A Radio Access Network (RAN) can contain central units (CUs) and distributed units (DUs). An NR base station (BS, such as a gNB, 5G Node B, Node B, transmission reception point (TRP), or access point (AP)) can correspond to one or more base stations. NR cells can be configured as access cells (ACells) or data-only cells (DCells). For example, the RAN (e.g., central units or distributed units) can configure these cells. DCells can be 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), and in others they may transmit synchronization signals. NR base stations can transmit downlink signals to user equipment (UEs) indicating the cell type. Based on the cell type indication, UEs can communicate with NR base stations. For example, UEs can determine the NR base station used for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0044] Figure 3An example logical architecture of a distributed radio access network 300 is illustrated according to aspects of this disclosure. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be the central unit of the distributed radio access network. 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 (also referred to as base stations, NR base stations, Node B, 5G NB, AP, or other terms). As mentioned above, TRP can be used interchangeably with "cell".

[0045] TRP 308 can be a Distributed Unit (DU). A TRP can connect to one ANC (ANC 302) or multiple ANCs (not shown). For example, for RAN sharing, radio as a service (RaaS), and service-specific ANC deployments, a TRP can connect multiple ANCs. A TRP can contain one or more antenna ports. A TRP can be configured to provide services to user equipment individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0046] The local architecture of the distributed radio access network 300 can be used to illustrate the fronthaul definition. This architecture can define fronthaul solutions that support different deployment types. For example, the architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter). The architecture can share features and / or components with LTE. Depending on various aspects, the next-generation access node (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for both LTE and NR.

[0047] This architecture enables collaboration between and within TRPs 308. For example, collaboration can be pre-defined within a TRP and / or implemented across TRPs via ANC 302. Depending on various factors, inter-TRP interfaces may be unnecessary or nonexistent.

[0048] Depending on various factors, the architecture of the Distributed Radio Access Network 300 can have a dynamic configuration with logical function partitioning. PDCP, RLC, and MAC protocols can be adaptively placed in the ANC or TRP.

[0049] Figure 4An example physical architecture of a distributed radio access network 400 is illustrated according to various aspects of this disclosure. 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 locally carry core network functions. The C-RU can be distributed. The C-RU can be closer to the network edge. A distributed unit (DU) 406 can carry one or more TRPs. The DU can be located at the network edge and has radio frequency (RF) capabilities.

[0050] Figure 5 Figure 500 illustrates a multi-RAT wireless communication environment where network operators may need to manage the use of radio access technologies. The figure shows a user equipment 502 capable of connecting multiple radio access technologies, including a 2G base station (BTS / BSC) 518, a 3G base station (NodeB / RNC) 516, a 4G base station (eNB) 504, and a 5G base station (gNB) 506. The 4G base station 504 interfaces with an EPC 512 containing a Mobility Management Entity (MME) 508, while the 5G base station 506 interfaces with a 5GC 514 containing an Access and Mobility Management Function (AMF) 510.

[0051] In modern wireless networks, network operators face a growing need to optimize their network resources across multiple radio access technologies. A typical scenario involves a multi-capable user equipment (UE) 502 capable of operating on the same Public Land Mobile Network (PLMN), which can function on GERAN (2G), UTRAN (3G), E-UTRAN (4G), or NG-RAN (5G). Network operators need mechanisms to control which specific radio access technologies (RATs) UE 502 can use in their network to manage network load, encourage migration to new technologies, or optimize spectrum usage. For example, when UE 502 registers to a 5G network via gNB 506 and Access and Mobility Management Function (AMF) 510, the operator may want to prevent the UE from falling back to a 4G network served by eNB 504, even if 4G coverage exists in the same geographic area.

[0052] In the first option, such as Figure 5 Implementing usage control for such radio access technologies in heterogeneous network environments presents significant challenges. A major issue is the lack of backward compatibility mechanisms when introducing this new capability. Legacy user equipment that does not support radio access technology restriction functions may receive restriction commands from the Mobility Management Entity (MME) 508 or the Access and Mobility Management Function 510, but may be unable to correctly interpret or process these commands. This can lead to unpredictable behavior in the network, with legacy equipment potentially ignoring critical network management commands or responding inappropriately to restriction messages.

[0053] In the first option, such as Figure 5 Another fundamental issue in the illustrated multi-radio access technology architecture is the ambiguity regarding the scope of radio access technology restrictions. When the network decides to restrict user equipment 502's access to certain radio access technologies, it is unclear whether these restrictions apply only to the current Tracking Area Identity (TAI) where the user equipment is located, extend to the entire registration area managed by Mobility Management Entity 508 or Access and Mobility Management Function 510, cover all Tracking Area Identity within the current Public Land Mobile Network, or also include the equivalent Public Land Mobile Network with a roaming agreement with the home network. This ambiguity becomes particularly complex when user equipment 502 moves between different geographical areas served by different base stations 504, 506, 516, or 518, each of which may have different restriction requirements.

[0054] In the first scenario, the multi-radio access technology environment also raises issues regarding emergency service handling. When user equipment 502 needs to make an emergency call, it must be able to select any available radio access technology to ensure public safety. However, if radio access technology restrictions exist, there is no clear mechanism to determine whether user equipment 502 should cover these restrictions for emergency services. For example, if user equipment 502 is restricted from using the 4G network via eNB 504, but only 4G coverage is available when an emergency call is needed, the system must provide clear guidance on whether the restriction should be followed or circumvented.

[0055] Furthermore, in the first scheme, the distributed nature of the control plane entities located in different core networks presents coordination challenges. Mobility management entity 508 manages 4G connectivity mobility in the Evolved Packet Core (EPC) 512, while access and mobility management function 510 handles 5G mobility management in the 5G Core (5GC) 514. When implementing radio access technology restrictions across multiple technologies, the lack of a standardized mechanism between these entities to coordinate or communicate restriction policies can lead to inconsistencies in the application of restrictions when user equipment 502 moves between different radio access technology domains.

[0056] In the second option, such as Figure 5 The multi-access wireless communication environment illustrated implements a capability negotiation mechanism to address the backward compatibility and operational ambiguity challenges identified in the first scheme. User equipment 502 can explicitly indicate to the network its support for wireless access technology usage control before any restriction policy is applied. When user equipment 502 initiates registration with the network, it includes a capability indication of its ability to correctly process and execute wireless access technology restriction commands from the network infrastructure.

[0057] In one implementation, capability negotiation begins with User Equipment 502 sending its initial registration or attach request to the network. For a 4G connection via eNB 504, User Equipment 502 sends an ATTACH REQUEST message to Mobility Management Entity 508 within Evolved Packet Core 512. In this message, User Equipment 502 sets the bit named Radio Access Technology Utilization Control (RATUC) to "Support" in the User Equipment Network Capability Information Element (IE). This explicitly indicates to Mobility Management Entity 508 that User Equipment 502 possesses the functionality required to receive, interpret, and enforce radio access technology restriction policies. Similarly, for a 5G connection via gNB 506, User Equipment 502 includes the RATUC capability bit in the 5GMM capability information element of the REGISTRATION REQUEST message sent to Access and Mobility Management Function 510 within 5G Core Network 514.

[0058] Upon receiving a capability indication from user equipment 502, the network entity makes an informed decision on whether to apply radio access technology usage control based on the received capability indication. If mobility management entity 508 receives an ATTACH REQUEST message with the RATUC bit set to "Supported" and determines that radio access technology restrictions should be applied based on operator policy, a radio access technology usage control information element is included in the subsequent ATTACH ACCEPT message sent to user equipment 502. This information element contains a specific list of restricted radio access technologies and the scope of application of these restrictions. The network follows a similar pattern in other mobility management procedures, such as including the radio access technology usage control information element in the TRACKING AREA UPDATE ACCEPT message when user equipment 502 performs a location update and maintains the capability indication.

[0059] The second approach offers flexibility in its messaging mechanism to adapt to various network scenarios and timing requirements. In the 5G domain, the Access and Mobility Management function 510 can not only transmit radio access technology restriction policies during initial registration via the REGISTRATION ACCEPT message, but also dynamically via the CONFIGURATION UPDATE COMMAND message. This allows the network to modify restriction policies without requiring the user equipment 502 to execute a new registration procedure, enabling more responsive network management. The CONFIGURATION UPDATE COMMAND message can include radio access technology usage control information along with other configuration parameters, providing an efficient policy update mechanism.

[0060] In the second approach, the network entity sends the list of radio access technology restrictions only to user equipment that has explicitly indicated support for the function. If user equipment 502 does not include a RATUC capability indication in its request message, or if the capability bit indicates that the function is not supported, the mobility management entity 508 or the access and mobility management function 510 will not include the radio access technology usage control information element in its response message. This design addresses backward compatibility issues by preventing legacy devices from receiving commands they cannot handle. Legacy user equipment that does not support the function continues to operate normally without receiving restriction commands, thus maintaining predictable behavior in a heterogeneous device ecosystem.

[0061] The list of restrictions on radio access technologies for network transmission includes scope information, clearly defining the geographical and logical boundaries to which the restrictions apply. The network can specify whether these restrictions apply to the current public terrestrial mobile network where user equipment 502 is registered, an equivalent public terrestrial mobile network with a roaming agreement with its home network, a specific tracking area identifier, or the entire registration area. This fine-grained control allows network operators to implement complex policies that can vary based on location, network load, or service demands. For example, a restriction preventing user equipment 502 from accessing the 4G network via eNB 504 might only apply to specific urban areas with strong 5G coverage via gNB 506, while allowing 4G access in rural areas with limited 5G deployment.

[0062] The second approach specifically addresses emergency service needs through explicit exemption rules. When User Equipment (UE) 502 needs to initiate emergency service, no Radio Access Technology (RAT) restrictions received from the network will apply. Even if UE 502 is restricted from using certain RATs (such as using a 3G network via NodeB / RNC 516) or using a 2G network via BTS / BSC 518 to provide normal service, these RATs remain available during emergency calls. This exemption is unconditional and takes precedence over all restriction policies, placing public safety above network management objectives. When UE 502 performs cell selection and reselection procedures during emergency service, the Radio Access Technology restriction list is disregarded, allowing it to camp on any available cell when emergency access is needed, regardless of the RAT type.

[0063] In addition to the primary capability negotiation mechanism, the second approach provides alternative configuration methods to adapt to different deployment scenarios and operator preferences. Radio access technology restriction information can be transmitted to the UE 502 via USIM configuration, where restriction policies are pre-configured on the user identity module. This method allows operators to configure restrictions before distributing devices to users. Furthermore, this approach supports transmission via management objects (MOs) (such as NAS MOs) or security packets, providing over-the-air configurability that can be updated without a network registration process. These alternative methods complement the primary signaling-based approach, providing operators with flexible deployment options.

[0064] In one implementation, when UE 502 receives a Radio Access Technology Use Control Information Element (IE) from Mobility Management Entity (MME) 508 or Access and Mobility Management Function (AMF) 510, it stores the restriction information and replaces any previously stored restrictions with the newly received policy. If subsequent network messages do not contain a Radio Access Technology Use Control IE, UE 502 interprets this as an indication to remove all restrictions and considers all radio access technologies available for selection. This stateful behavior provides a clear and predictable restriction lifecycle, allowing network operators to achieve consistent policy enforcement across multi-RAT infrastructures.

[0065] Furthermore, the following rules can be defined according to the second scheme. For 4G systems, according to the rules, network operators can restrict user access to certain radio access technologies, where radio access technologies refer to GERAN, UTRAN, E-UTRAN, or NG-RAN, as defined in 3GPP TS 36.304 and 3GPP TS 38.304. The network can send a radio access technology usage control information element (IE) to UE 502 through a specific Non-Access Stratum (NAS) message, specifically an ATTACHACCEPT message or a TRACKING AREA UPDATE ACCEPT message.

[0066] The capability negotiation protocol is implemented through dedicated bits in the UE network capability information element (IE). When UE 502 supports the Radio Access Technology Use Control (RAC) function, the RATUC bit is set to "RAC Support" in the UE network capability IE sent to the MME 508 in the ATTACH REQUEST message. This single bit serves as an explicit capability declaration, informing the network UE 502 whether it possesses the protocol stack implementation required to process and enforce RAC restriction policies. The location of this capability indication in the existing UE network capability IE maintains backward compatibility with the existing message structure while adding new functionality.

[0067] Network-side behavior is precisely defined as dependent on UE capability indications. If UE 502 indicates support for Radio Access Technology Use Control (RATC) in its ATTACH REQUEST message, and the network decides to apply RATC based on operator policy, then MME 508 should include the RATC IE in its ATTACH ACCEPT message. This conditional inclusion mechanism prevents the network from sending restriction commands to devices unable to process restriction commands. MME 508 must not indicate "E-UTRAN Restricted" in the RATC IE to prevent situations where the UE is restricted from using E-UTRAN itself when connected to it.

[0068] The UE's behavior upon receiving a Radio Access Technology (RAT) Use Control IE is governed by explicit state management rules. When the ATTACH ACCEPT message contains an RATT Use Control IE, UE 502 stores the received RATT Use Control information and replaces any previously stored restriction information with the newly received policy. This replacement mechanism provides a clear state transition and avoids the accumulation of potentially conflicting restriction policies. Conversely, if the ATTACH ACCEPT message does not contain an RATT Use Control IE, UE 502 deletes any stored RATT Use Control information and considers all radio access technologies unrestricted, providing a clear restriction removal mechanism.

[0069] A similar procedure applies to mobility management scenarios via the TRACKING AREA UPDATE procedure. If UE 502 indicates support for Radio Access Technology Use Control (RATC) in the TRACKING AREA UPDATE REQUEST message, and the network decides to apply RATC, then MME 508 should include the RATC use control IE in the TRACKING AREA UPDATE ACCEPT message. This parallel implementation maintains consistency between different mobility procedures and allows the network to update restriction policies as UE 502 moves between tracking areas.

[0070] The structure of the information element is also defined. This IE is used to indicate restricted radio access technologies. The purpose of the radio access technology control information element is for the network to communicate restricted radio access technologies to the UE. These definitions establish the radio access technology control IE as a network-to-UE information element specifically designed to convey restriction policies.

[0071] The rules also include consideration of the Public Land Mobile Network (PLMN) selection process. UE 502 prohibits any PLMN or combination of radio access technologies with radio access technology restrictions from being considered as a candidate PLMN for selection, as specified in 3GPP TS 23.122. This requirement extends the impact of radio access technology restrictions from cell selection within a PLMN to mobility decisions across PLMNs, thereby comprehensively implementing operator strategies across various network selection scenarios.

[0072] For 5G systems (5GS), similar rules define radio access technology (RAN) usage control mechanisms and are adapted for the 5G architecture. Network operators can restrict user access to certain RAN technologies within the 5G domain, including GERAN, UTRAN, E-UTRAN, or NG-RAN, as specified in 3GPP TS 36.304 and 3GPP TS 38.304. In the 5G core network (5GC) 514, AMF 510, as the primary control plane entity, is responsible for transmitting RAN restriction policies to UE 502. The network transmits RAN usage control information elements to UE 502 via REGISTRATION ACCEPT messages, establishing the initial restriction policy during the registration process.

[0073] The capability negotiation protocol in 5GS follows a similar pattern to 4G, but uses 5G-specific signaling elements. When UE502 supports Radio Access Technology Use Control (RAC) functionality, the RATUC bit is set to "RAC Support" in the 5G Mobility Management (5GMM) capability IE of the REGISTRATIONREQUEST message sent to AMF 510 via gNB 506. The position of this capability indication in the 5GMM capability IE is consistent with the 5G protocol architecture, while providing the same explicit capability declaration functionality as in 4G systems. The positioning of the RATUC bit in the 5GMM capability IE is consistent with the 5G non-access stratum protocol structure for capability exchange between UE502 and AMF 510.

[0074] When UE 502 indicates support for Radio Access Technology Use Control (RATC) in its REGISTRATION REQUEST message, and AMF 510 determines that RTC restrictions should be applied based on operator policy, AMF 510 includes the RTC RATC use control IE in the REGISTRATION ACCEPT message. This conditional inclusion mechanism maintains the backward compatibility principles established in the overall system design. AMF 510 follows similar logic to MME 508 to prevent conflicting restrictions, particularly avoiding indicating "NG-RAN restricted" when UE 502 is connected via NG-RAN, to maintain logical consistency in the restriction policy.

[0075] A significant improvement in the 5G system (5GS) implementation is the introduction of dynamic configuration capabilities through a general user equipment configuration update process. The Access and Mobility Management Function (AMF) 510 can initiate this process at any time during an established 5G connection by sending a CONFIGURATION UPDATE COMMAND message to the User Equipment (UE) 502. The CONFIGURATION UPDATE COMMAND message can contain radio access technology usage control information, as well as numerous other configuration parameters, such as 5G-GUTI, a list of Tracking Area Identifiers (TAIs), Allowed Network Slice Selection Auxiliary Information (NSSAI), Local Access Data Network (LADN) information, a list of service areas, a MICO indication, configured NSSAI, a network slice subscription change indication, operator-defined access category definitions, and various other 5G-specific parameters. This capability enables the 5G core network (5GC) 514 to dynamically modify radio access technology restriction policies without requiring user equipment 502 to perform a new registration process, providing more responsive and flexible network management compared to 4G systems which mainly update during the attach or track area update process.

[0076] User equipment (UE) behavior in 5GS follows the same state management principles established for the entire system. When a REGISTRATION ACCEPT message contains Radio Access Technology (RAT) usage control information elements, UE 502 stores the received restriction information and replaces any previously stored RAT usage control information with the newly received policy. This replacement mechanism maintains clarity in state transitions across technology generations. Similarly, when a CONFIGURATION UPDATE COMMAND message contains updated RAT usage control information, UE 502 applies the same store and replace logic, ensuring consistency regardless of the message type used for policy delivery. If a subsequent REGISTRATION ACCEPT message or related configuration message does not contain RAT usage control information elements, UE 502 interprets this absence as an instruction to remove all RAT restrictions and considers all RATs available for selection.

[0077] Information element definitions and Public Land Mobile Network (PLMN) selection behavior are consistent with system-wide principles in 5GS. Radio access technologies use control information elements to pass restricted radio access technologies from the network to user equipment 502, maintaining consistency in both 4G and 5G implementations. User equipment 502, operating under 5GS, follows the same PLMN selection restriction rules, and does not consider any PLMN and radio access technology combination with valid radio access technology restrictions as a candidate PLMN, as specified in 3GPP TS 23.122.

[0078] Figure 6 Flowchart 600 illustrates a method for obtaining and applying a list of restrictions for Radio Access Technology (RAT) from a network. This method can be performed by user equipment (such as user equipment 104, 250, or 502).

[0079] In operation 602, the user equipment sends a capability indication to the network, indicating support for radio access technology restriction functions. In some implementations, to send the capability indication, the user equipment uses existing or dedicated information elements in a message between the user equipment and the network to indicate support for radio access technology restriction functions. This message from the user equipment is either an ATTACH REQUEST message or a REGISTRATION REQUEST message.

[0080] In operation 604, when the user equipment indicates support for this function, the user equipment receives a restricted radio access technology information list from the network. In some implementations, the restricted radio access technology information list is received via one of the following: a CONFIGURATION UPDATE COMMAND message, a REGISTRATION ACCEPT message, or a SERVICE ACCEPT message. The restricted radio access technology information list contains applicability information indicating that the list applies to one or more of the following: the current public land mobile network, a registered public land mobile network, an equivalent public land mobile network, a registered area, or a tracking area identifier belonging to the current public land mobile network, a registered public land mobile network, or an equivalent public land mobile network.

[0081] In Operation 606, the User Equipment (UE) applies a restricted radio access technology (RAT) information list to cell selection and reselection for non-emergency services. In some implementations, to apply the RAT information list, the UE does not use the RAT for cell selection and reselection within a specified applicable range.

[0082] In some implementations, user equipment (UEs) do not use the restricted list of radio access technologies during emergency service. To avoid using the restricted list during emergency service, UEs may use radio access technologies from the restricted list for cell selection and reselection during emergency service.

[0083] In some implementations, the user equipment receives restricted radio access technology information via one of the following: USIM configuration, management objects, or security data packets.

[0084] In some implementations, the user equipment ignores the list or the network does not send the list when the user equipment does not indicate that the feature is supported.

[0085] Figure 7 A flowchart 700 illustrates a method for managing wireless access technologies. This method may be performed by one or more network entities, such as the Mobility Management Entity (MME) of a 4G network or the Access and Mobility Management Function (AMF) of a 5G network.

[0086] In operation 702, one or more network entities receive a capability indication from the user equipment, indicating whether the user equipment supports the radio access technology restriction function. In operation 704, one or more network entities determine whether to apply radio access technology usage control based on the received capability indication. In operation 706, when the user equipment indicates support for the radio access technology restriction function, one or more network entities send a list of restricted radio access technologies to the user equipment.

[0087] In some implementations, to receive a capability indication, one or more network entities receive the capability indication in an existing or dedicated information element of a message from the user equipment. This message from the user equipment is either an ATTACHREQUEST message or a REGISTRATION REQUEST message. To send a restricted radio access technology information list, one or more network entities send the list in an ATTACH ACCEPT message or a REGISTRATION ACCEPT message. In some implementations, the restricted radio access technology information list is sent in one of the following ways: a CONFIGURATION UPDATE COMMAND message, a REGISTRATION ACCEPT message, or a SERVICE ACCEPT message. When the user equipment does not indicate support for the restricted radio access technology function, one or more network entities do not send the restricted radio access technology information list.

[0088] In some implementations, the Restricted Radio Access Technology Information List indicates radio access technologies that are restricted in non-emergency services but remain available in emergency services. The Restricted Radio Access Technology Information List includes applicability information indicating that the list applies to one or more of the following: the current public land mobile network, a registered public land mobile network, an equivalent public land mobile network, a registered area, or a tracking area identifier belonging to the current public land mobile network, a registered public land mobile network, or an equivalent public land mobile network. The Restricted Radio Access Technology Information List specifies one or more of the following restrictions: GERAN, UTRAN, E-UTRAN, or NG-RAN.

[0089] In some implementations, one or more network entities provide restricted radio access technology information to user equipment through one of the following: USIM configuration, management objects, or security packets.

[0090] In addition, such as Figure 5 As shown in the multi-wireless access technology environment, user equipment 502 may include and Figure 2 The block diagram of User Equipment 250 shows similar hardware components. Specifically, User Equipment 502 may include one or more antennas 252, transceivers (including transmitter 254TX and receiver 254RX), transmit (TX) processor 268, receive (RX) processor 256, memory 260, and a central controller / processor 259. These components together enable User Equipment 502 to communicate with various network entities under different wireless access technologies, such as eNB 504 and gNB 506.

[0091] Furthermore, the controller / processor 259 of user equipment 502, in conjunction with program code and data stored in memory 260, is specifically configured to implement a method for negotiating and applying Radio Access Technology (RAT) restrictions. The controller / processor 259 instructs the TX processor 268 to generate and transmit capability indications, such as the RATUC bit in an ATTACH REQUEST or REGISTRATION REQUEST message, to a network entity such as the Mobility Management Entity (MME) 508 or the Access and Mobility Management Function (AMF) 510. Subsequently, after receiving a list of restricted radio access technology information, such as an ATTACH ACCEPT or CONFIGURATION UPDATE COMMAND message, via the RX processor 256, the controller / processor 259 stores this list in memory 260 and applies the restrictions for cell selection and reselection during non-emergency service periods, thereby achieving the backward-compatible radio access technology usage control described above.

[0092] Network-side operations can be performed by one or more network entities, such as the MME 162 within the EPC 160 in a 4G system, or the AMF 192 within the 5GC 190 in a 5G system. These core network entities are configured to perform these operations. Figure 7 The method described herein. Specifically, such an entity includes at least one processor, a memory communicatively connected to the processor, and a network interface. When executing instructions stored in the memory, the processor is configured to receive a capability indication from user equipment 104, indicating support for wireless access technology restriction functions. Based on this indication, the processor determines whether wireless access technology use control should be applied and generates a list of restricted wireless access technologies, which is included in a Non-Access Stratum (NAS) message (e.g., ATTACH ACCEPT, REGISTRATION ACCEPT, or CONFIGURATION UPDATE COMMAND) and sent to user equipment 104.

[0093] NAS messages generated by MME 162 or AMF 192 are forwarded to base stations (e.g., base stations 102, 210) for direct wireless transmission to user equipment 104. Base station 210 includes a controller / processor 275 associated with memory 276, one or more transmitters 218TX, and one or more antennas 220. Controller / processor 275 is configured to receive NAS messages containing a list of restricted radio access technologies from the core network. Controller / processor 275 provides data to TX processor 216 for transmission, which performs Layer 1 processing such as encoding and modulation. The resulting signal is then up-converted by transmitter 218TX via antenna 220 and transmitted to user equipment. Conversely, base station antennas 220, receivers 218RX, RX processor 270, and controller / processor 275 are configured to receive initial request messages from user equipment containing capability indications and forward them to the appropriate core network entity (MME or AMF).

[0094] It should be understood that the specific order or hierarchy of modules in the disclosed process / flowchart is merely exemplary. The specific order or hierarchy of modules in the process / flowchart may be rearranged according to design preferences. Furthermore, some modules may be combined or omitted. The accompanying method claims present the module elements in an exemplary order and are not limited to the specific order or hierarchy shown.

[0095] The foregoing description is intended to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be readily 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 limit the aspects shown herein, but rather to provide a full scope consistent with the language of the claims, wherein a reference to a single element does not imply "only one," unless explicitly stated otherwise, but rather refers to "one or more." The term "exemplary" is used herein to mean "as an example, instance, or illustration." Any aspect described as "exemplary" is not necessarily to be construed as preferred or superior to other aspects. Unless explicitly stated otherwise, the term "some" means one or more. Combinations such as "at least one A, B, or C," "one or more A, B, or C," "at least one A, B, and C," "one or more A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one A, B, or C", "one or more A, B, or C", "at least one A, B, and C", "one or more A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the aspects described in this disclosure, whether known or subsequently known to those skilled in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, the disclosure herein is not intended for public disclosure, whether or not it is expressly recited in the claims. The terms "module," "mechanism," "element," "device," etc., should not replace the word "means." Therefore, unless an element expressly uses the phrase "means for...", no claim element should be construed as a means plus a functional element.

Claims

1. A method for wireless communication by a user equipment, comprising: Send a capability indication to the network, indicating support for wireless access technology restriction functions; When the network receives an indication from the user equipment that it supports the function, it receives a list of restricted wireless access technologies from the network. as well as This list of restricted wireless access technologies is applied to cell selection and reselection for non-emergency services.

2. The method of claim 1, further comprising: The list of restricted wireless access technologies should not be used during emergency services.

3. The method of claim 2, wherein the list of restrictions on not using the wireless access technology during emergency services includes: During emergency service, the list of restricted wireless access technologies is used for cell selection and reselection.

4. The method of claim 1, wherein sending the capability indication comprises: In messages between the user equipment and the network, support for the wireless access technology restriction function is indicated using existing information elements or dedicated information elements.

5. The method of claim 4, wherein: The message from this user equipment is either an ATTACH REQUEST message or a REGISTRATION REQUEST message.

6. The method of claim 1, wherein the restricted wireless access technology information list is received via one of the following: a CONFIGURATION UPDATE COMMAND message, a REGISTRATION ACCEPT message, or a SERVICE ACCEPT message.

7. The method of claim 1, wherein the restricted wireless access technology information list includes applicability information indicating that the list is applicable to one or more of the following: Current public terrestrial mobile networks; Registered with public terrestrial mobile networks; Equivalent public terrestrial mobile network; Registration area; or The tracking area identifier belonging to the current public land mobile network, the registered public land mobile network, or the equivalent public land mobile network.

8. The method of claim 7, wherein the list of information on the application of the restricted wireless access technology includes: This restricted radio access technology shall not be used for cell selection and cell reselection within the specified applicable scope.

9. The method of claim 1, further comprising: Information about this restricted wireless access technology can be received through one of the following: USIM configuration, management objects, or security data packets.

10. The method of claim 1, wherein when the user equipment does not indicate support for the function, the user equipment ignores the list or the network does not send the list.

11. A method for one or more network entities to conduct wireless communication in a wireless communication network, comprising: Receive capability indication from user equipment to indicate whether the user equipment supports wireless access technology restriction functions; Based on the received capability indication, determine whether to apply wireless access technology use control; as well as When the user equipment indicates support for the wireless access technology restriction function, a list of restricted wireless access technologies is sent to the user equipment.

12. The method of claim 11, wherein the restricted wireless access technology information list indicates wireless access technologies that are restricted in non-emergency services but are still available in emergency services.

13. The method of claim 11, wherein receiving the capability indication comprises: Receive the capability indication in an existing information element or a dedicated information element in a message from the user equipment.

14. The method of claim 13, wherein: The message from the user equipment is either an ATTACH REQUEST message or a REGISTRATION REQUEST message; and The transmission includes sending the list of restricted radio access technology information in an ATTACH ACCEPT message or a REGISTRATION ACCEPT message.

15. The method of claim 11, wherein sending the list of restricted wireless access technologies includes: Send the list via one of the following: CONFIGURATION UPDATE COMMAND message, REGISTRATION ACCEPT message, or SERVICE ACCEPT message.

16. The method of claim 11, wherein the restricted wireless access technology information list includes applicability information indicating that the list is applicable to one or more of the following: Current public terrestrial mobile networks; Registered with public terrestrial mobile networks; Equivalent public terrestrial mobile network; Registration area; or The tracking area identifier belonging to the current public land mobile network, the registered public land mobile network, or the equivalent public land mobile network.

17. The method of claim 11, further comprising: The restricted wireless access technology information is provided to the user equipment through one of the following: USIM configuration, management objects, or security data packets.

18. The method of claim 11, further comprising: When the user equipment does not indicate support for the wireless access technology restriction function, the list of restricted wireless access technologies will not be sent.

19. The method of claim 11, wherein the one or more network entities include a mobility management entity of a 4G network or an access and mobility management function of a 5G network.

20. The method of claim 11, wherein the restricted radio access technology information list specifies one or more of the following restrictions: GERAN, UTRAN, E-UTRAN, or NG-RAN.

21. An apparatus for wireless communication, the apparatus being a user equipment, comprising: Memory; as well as At least one processor, coupled to the memory, is configured as follows: Send a capability indication to the network, indicating support for wireless access technology restriction functions; When the user equipment indicates that it supports the function, receive a list of restricted wireless access technologies from the network; as well as This list of restricted wireless access technologies is applied to cell selection and reselection for non-emergency services.

Images