Handling of new generation (6g) registration reject not supported

Abstract

A user equipment sends a registration request or a service request to a next generation core network through a next generation radio access network. The user equipment receives a reject message from the next generation core network, the reject message indicating that next generation services are not available for the user equipment. The user equipment performs one or more operations from a set of operations in response to receiving the reject message. As one operation from the set of operations, the user equipment sets an update status to a status indicating that registration on the next generation core network related to the next generation radio access network is not allowed. As another operation from the set of operations, the user equipment deletes a temporary identity related to the next generation core network. As another operation from the set of operations, the user equipment deletes last registration location information related to the next generation core network.

Description

[0001] Cross-references

[0002] This application claims priority to Indian Patent Application Serial No. 202421065628, entitled “Method for Processing Registration Not Supporting Next Generation (6G)”, filed on August 30, 2024, the entire contents of which are hereby expressly incorporated by reference. Technical Field

[0003] This disclosure relates generally to wireless communications, and more specifically to techniques for handling registration rejection and redirection for user equipment in next-generation wireless networks. 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 multiple access technologies to support 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 example of a telecommunications standard is 5G New Radio (5G 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. There remains 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 summary of one or more aspects to provide a basic understanding of them. This summary is not a comprehensive overview of all conceived aspects, nor is it intended to identify key or important elements of all aspects, nor does it limit the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description thereafter.

[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be user equipment (UE). The UE sends a registration request or service request to a next-generation core network via a next-generation radio access network (RAN). The UE receives a rejection message from the RAN indicating that the next-generation service is unavailable to the UE. In response to receiving the rejection message, the UE performs one or more of a set of operations. As one operation in the set of operations, the UE updates its status to indicate a state indicating that registration is not permitted on the RAN associated with the RAN. As another operation in the set of operations, the UE deletes a temporary identity associated with the RAN. As yet another operation in the set of operations, the UE deletes the last registration location information associated with the RAN.

[0009] In another 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 registration request or service request to a next-generation core network via a next-generation radio access network. The UE receives a rejection message from the next-generation core network, the rejection message containing a redirection reason indicating that the UE should be redirected to a legacy network. In response to receiving the rejection message with the redirection reason, the UE disables next-generation mode. Further, in response to receiving the rejection message with the redirection reason, the UE searches for a suitable cell connected to the legacy network indicated by the redirection reason.

[0010] In another 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 attempts to register with a 6G core network via a 6G radio access network. The UE receives a rejection message from the 6G core network, with a rejection reason value indicating that the UE does not support 6G services. The UE sets its 6GS update status to 6U3 roaming not allowed. The UE deletes its 6G Globally Unique Temporary Identifier (6G-GUTI). The UE deletes its last registered location information, including at least one Last Access Registration Tracking Area Identity (TAI) or a list of tracking area identities. The UE disables 6G mode for the public land mobile network (PLMN) associated with the 6G core network. The UE starts a timer associated with the disabled 6G mode. Upon expiration of the timer, the UE re-enables 6G mode for the public land mobile network.

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

[0012] Figure 1 This is a schematic diagram illustrating a wireless communication system and its access network.

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

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

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

[0016] Figure 5 An example of handling the registration process in a scenario where the network does not support 6G for some user devices is shown.

[0017] Figure 6 This is a flowchart illustrating the registration process when the next-generation network does not support user equipment services.

[0018] Figure 7 This is a flowchart illustrating the method for handling redirection during the registration process in next-generation wireless networks.

[0019] Figure 8 This is a flowchart illustrating the method for handling registration rejection in a 6G wireless network. Detailed Implementation

[0020] The following detailed description, 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 described concepts can be implemented. Specific details are included to provide a thorough understanding of the various concepts. However, those skilled in the art will understand that these concepts can be implemented without these specific details. In some cases, known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0021] 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 by various modules, components, circuits, processes, algorithms, etc. (collectively referred to as "elements") shown in the accompanying drawings. These elements can be implemented by electronic hardware, computer software, or any combination of both. Whether these elements are implemented in hardware or software depends on the specific application and design constraints of the overall system.

[0022] For example, a single element, any portion of an element, or any combination of elements can be implemented as a "processing system" containing 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 in this disclosure. One or more processors in a processing system can execute software. Software should be broadly understood as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or other names.

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

[0024] 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 a base station 102, user equipment 104, an 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.

[0025] 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. Among other functions, base station 102 can perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and alarm message delivery. Base stations 102 can 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 can be wired or wireless.

[0026] 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, 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 containing small cells and macro cells can be referred to as a heterogeneous network. Heterogeneous networks may also include Home Evolved Node Bs (HeNBs), 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 may be implemented using one or more carriers. Base station 102 / user equipment 104 may use spectrum with a bandwidth of up to 7 MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.), allocated in carrier aggregation with a total bandwidth of up to Yx MHz (x component carriers), for transmission in each direction. Carriers may be adjacent or non-adjacent. Carrier allocation may be asymmetrical between DL and UL (e.g., DL may be allocated more or fewer carriers than UL). Component carriers may include primary component carriers and one or more auxiliary component carriers. Primary component carriers may be referred to as primary cells (PCells), and auxiliary component carriers may be referred to as auxiliary cells (SCells).

[0027] 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 (WWAN) 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 using various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

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

[0029] Cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, cell 102' can employ New Radio Access (NR) technology and use the same 5 GHz unlicensed spectrum as Wi-Fi access point 150. Employing NR in unlicensed spectrum can enhance the coverage and / or increase the capacity of the access network.

[0030] 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 gNB180, 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 may 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 are referred to as millimeter waves. Near-millimeter waves extend down to 3 GHz with wavelengths of 100 mm. The ultra-high frequency (SHF) band ranges from 3 GHz to 30 GHz, also known as centimeter waves. When communicating using millimeter-wave / near-millimeter-wave radio frequency bands (e.g., 3 GHz to 300 GHz), path loss is extremely high and coverage is short. Millimeter-wave base station 180 can employ beamforming 182 with user equipment 104 to compensate for the extremely high path loss and short range.

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

[0032] 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 Gateway (MBMS Gateway) 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network Gateway (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. Typically, MME 162 provides bearer and connection management. All Internet Protocol (IP) packets from all users are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. 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 can provide and deliver MBMS user services. BM-SC 170 can serve as an entry point for content provider MBMS delivery, authorizing and initiating MBMS bearer services within a public land mobile network (PLMN), and scheduling MBMS delivery. MBMS Gateway 168 can distribute MBMS traffic to base station 102, which belongs to a Multicast Broadcast Single Frequency Network (MBSFN) area and broadcasts specific services, and can be responsible for session management (start / stop) and collecting billing information related to enhanced MBMS (eMBMS).

[0033] 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 User Equipment 104 and the core network 190. Typically, the SMF 194 provides QoS streaming and session management. All Internet Protocol (IP) packets from all users are transmitted through the UPF 195. The UPF 195 provides IP address allocation for User Equipment and other functions. The UPF 195 connects to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), packet-switched streaming media services, and / or other IP services.

[0034] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base transceiver station, wireless base station, wireless transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or other suitable terms. Base station 102 provides user equipment 104 with access to the 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 radios, GPS devices, 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 rate 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 suitable terms.

[0035] Although this disclosure may relate to 5G New Radio (NR), it may also be applied to other similar fields, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other radio / wireless access technologies.

[0036] Figure 2This is a block diagram illustrating communication between a base station 210 and a user equipment (UE) 250 in the access network. In the downlink, IP packets from the Evolved Packet Core (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), Different Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; 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), RLC service data unit (SDU) connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing MAC SDUs to transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority.

[0037] Transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical layer (PHY), 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)). Encoded and modulated symbols can 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 obtained from reference signals transmitted by UE 250 and / or channel state feedback. 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 radio frequency carrier.

[0038] At UE 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 this 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 streams directed toward UE 250. If there are multiple spatial streams directed toward UE 250, the RX processor 256 can synthesize them 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. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 210. 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. The data and control signals are then provided to controller / processor 259, which implements Layer 3 and Layer 2 functions.

[0039] 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.

[0040] Similar to the functions related to downlink transmission of base station 210, controller / processor 259 provides RRC layer functions related to system information (e.g., MIB, SIBs) 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, RLC SDU connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing MAC SDUs to TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority.

[0041] The channel estimate obtained by the channel estimator 258 based on the reference signal or feedback transmitted by the base station 210 can be used by the TX processor 268 to select appropriate coding and modulation schemes 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 the radio frequency carrier. The uplink transmission is processed at the base station 210 in a manner similar to the reception function at the UE 250. Each receiver 218RX receives the signal through its corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the radio frequency carrier and provides this information to the RX processor 270.

[0042] Controller / processor 275 may be associated with memory 276, which stores program code and data. Memory 276 may be referred to as computer-readable medium. In the 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 Evolved Packet Core (EPC) 160. Controller / processor 275 is also responsible for error detection using ACK and / or NACK protocols to support Hybrid Automatic Repeat Request (HARQ) operation.

[0043] New radio (NR) can refer to a wireless device configured to operate based on a new air interface (e.g., an air interface based on Orthogonal Frequency Divisional Multiple Access (OFDMA)) or a fixed transport layer (e.g., a non-Internet Protocol (IP)). NR can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in both uplink and downlink, and can include support for half-duplex operation using time division duplexing (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).

[0044] 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 for 0.25 ms, or a bandwidth of 30 kHz for 0.5 ms (similarly, a 15 kHz subcarrier spacing (SCS) provides a 50 MHz bandwidth over a 1 ms duration). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR slots) with a length of 10 ms. Each slot can indicate the link direction (i.e., downlink or uplink) for data transmission, and the link direction of each slot can be dynamically switched. Each slot can include downlink / uplink data and downlink / uplink control data. NR uplink and downlink slots can be combined as follows. Figure 5 and Figure 6 More detailed description.

[0045] NR radio access networks may include central units (CUs) and distributed units (DUs). NR base stations (e.g., gNBs, 5G Node Bs, Node Bs, transmission reception points (TRPs), access points (APs)) may correspond to one or more base stations. NR cells may be configured as access cells (ACells) or data-only cells (DCells). For example, the radio access network (e.g., central units or distributed units) may configure these cells. DCells may be data-only cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or handover. In some cases, DCells may not transmit synchronization signals (SS), and in others they may transmit synchronization signals. NR base stations may transmit downlink signals to user equipment indicating the cell type. Based on the cell type indication, user equipment can communicate with the NR base station. For example, user equipment can determine the NR base station used for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0046] Figure 3 An example logical architecture of a distributed radio access network 300 according to aspects of this disclosure is shown. 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. Backhaul interfaces to the next-generation core network (NG-CN) 304 may terminate at the ANC. Backhaul interfaces to adjacent next-generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (also referred to as base stations, NR base stations, node Bs, 5G node Bs, access points, or other terms). As mentioned above, TRPs can be used interchangeably with "cells".

[0047] 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 radio access network sharing, radio as a service (RaaS), and service-specific ANC deployments, a TRP can connect to multiple ANCs. A TRP can include 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).

[0048] The local architecture of the distributed radio access network 300 can be used to illustrate the fronthaul definition. This architecture can be defined as a fronthaul solution supporting 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 Long Term Evolution (LTE). Depending on certain aspects, the Next Generation Access Node (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.

[0049] This architecture enables collaboration between and within TRPs 308. For example, collaboration can be pre-defined within a TRP and / or across TRPs via ANC 302. Depending on certain aspects, inter-TRP interfaces may not be required or may not exist.

[0050] Depending on certain aspects, the architecture of the distributed radio access network 300 can have a dynamic configuration of segmentation logic functions. Packet Data Convergence Protocol (PDCP), Radio Link Control Protocol (RLC), and Media Access Control Protocol (MAC) can be adaptively placed in the ANC or TRP.

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

[0052] Figure 5 Figure 500 illustrates an example of a registration process in a scenario where the network does not support 6G for certain user devices. In this example, user device 504 represents a user device capable of 6G communication, but may encounter problems when attempting to register or request services on a network that temporarily or permanently does not support that particular user device due to subscription restrictions or network incompatibility. 6G base station 502 acts as a base station providing 6G radio access network (6G-RAN) access, through which user device 504 attempts to execute the registration or service request process. However, in the case where the network cannot provide access, in this first scenario, the network lacks a specified mechanism to notify user device 504, and subsequent actions by user device 504 are undefined, potentially leading to inefficiencies in handling such rejections.

[0053] Connected to 6G base station 502 is 6G core network 540. As the core network of the 6G system, it is responsible for handling registration requests from user equipment 504 and may send a rejection message if it cannot provide 6G support for user equipment 504. In the initial deployment phase of 6G, not all operators fully support 6G. In this first scenario, when 6G-capable user equipment like user equipment 504 attempts to register on the 6G network, there is no explicit resolution path. Furthermore, 5G base station 512, as a base station (gNB) providing access to 5G core network 550, can serve as a redirection target when 6G core network 540 cannot accommodate user equipment 504.

[0054] Furthermore, 4G base station 522, acting as an eNB providing EPC 560 access, offers user equipment 504 an alternative redirection option when 6G is not supported. EPC 560, or Evolved Packet Core, is the core network of the 4G system.

[0055] Therefore, in the first scheme, a process needs to be defined to handle handover when the network refuses access via 6G-RAN for any reason (such as subscription issues). When the network does not support 6G for a user device, the network has not established a way to notify the user device, and further actions for the user device are not specified, which may lead to lengthy attempts or inefficient network selection.

[0056] See Figure 5In the second scheme, when user equipment 504 performs a registration process and / or a service request process through a next-generation RAT (such as through a 6G base station 502 providing 6G-RAN access), if the 6G core network 540 is unable to provide access to user equipment 504 for any reason (such as subscription restrictions or lack of support), the 6G core network 540 can reject user equipment 504 using a new reason value. This new reason value explicitly indicates that 6G services are unavailable to user equipment 504, providing the network with a clear mechanism to notify user equipment 504 of the reason for rejection.

[0057] When User Equipment 504 receives this new reason from the 6G core network 540, User Equipment 504 performs one or more predefined operations to properly handle the rejection. User Equipment 504 sets its internal 6GS update state to 6U3 Roaming Not Allowed, a state similar to the 5U3 Roaming Not Allowed state used in 5G systems. This state indicates that User Equipment 504's last registration or service request process was executed correctly, but the 6G core network 540 responded negatively due to roaming or subscription restrictions. Therefore, User Equipment 504 recognizes that the registration process has been rejected by the network and continues to perform appropriate cleanup and rollback operations.

[0058] User equipment 504 can delete any temporary identities associated with 6G, such as the 6G Globally Unique Temporary Identifier (6G-GUTI), which may have been assigned or stored. Furthermore, user equipment 504 deletes the last registration location information stored for 6G, including the Last Access Registration Tracking Area Identifier (TAI) and a list of tracking area identifiers. User equipment 504 also resets its attempt counters, which could be registration attempt counters or service request attempt counters, to prepare for future registration attempts on other networks.

[0059] In addition, user equipment 504 can choose to enter a restricted service state, a cellless state, or a public land mobile network search state, depending on implementation and network conditions, in order to restore or seek other networks. For example, user equipment 504 can disable the 6G mode of a specific public land mobile network (PLMN), or add that PLMN or standalone non-public network (SNPN) to an existing or new disabled list, preventing immediate reselection of an unsupported 6G option.

[0060] To manage temporary disabling, when user equipment 504 disables 6G mode for this PLMN, user equipment 504 starts timer 532. This timer can be a new timer specifically designated for 6G disabling or an existing timer reused for this function. Timer 532 prevents user equipment 504 from immediately retrying 6G registration on the same PLMN, allowing time for potential resolution of network conditions or subscription issues. When timer 532 expires, user equipment 504 removes the PLMN or the combination of a PLMN and 6G capability from the disabled list or prohibited list, enabling user equipment 504 to potentially retry 6G access on that PLMN in the future.

[0061] When the PLMN is on the 6G disabled or disabled list, user equipment 504 will not select a 6G PLMN, SNPN, or RAT during the PLMN selection process. Instead, user equipment 504 can attempt to connect via other networks, such as the 5G network via 5G base station 512 and 5G core network 550, or the 4G network via 4G base station 522 and EPC 560. This mechanism provides a structured fallback method when 6G services are unavailable, allowing user equipment 504 to maintain connectivity via the legacy network while periodically checking the availability of 6G services after timer 532 expires.

[0062] See you again Figure 5 In the third scenario, user equipment 504 can be a cellular Internet of Things (CIoT) device or any user equipment requiring network redirection for optimization. When user equipment 504 performs a registration process and / or service request process to the 6G core network 540 via the 6G base station 502, the 6G core network 540 can determine that it cannot provide service to user equipment 504 in the 6G system, but can provide service through the traditional network. This determination can be based on various factors, including cellular IoT optimization, where some IoT devices may receive better service through a traditional network that provides more suitable coverage or power consumption characteristics for IoT applications.

[0063] In such scenarios, the 6G core network 540 rejects registration or service requests with a specific reason value indicating the required redirection. When the 6G core network 540 determines that user equipment 504 can only be provided through the 4G network, it sends a rejection message with the reason value #31 "Redirection required to Evolved Packet Core (EPC)". This reason indicates that the 6G core network 540 cannot provide service to user equipment 504 in any system other than EPC 560, instructing user equipment 504 to connect through 4G base station 522. Similarly, when the 6G core network 540 determines that user equipment 504 should be provided through the 5G network instead of the 6G network, it sends a rejection message with a new reason value #xx "Redirection required to 5G Core (5GC)", instructing user equipment 504 to connect to the 5G core network 550 through 5G base station 512.

[0064] Upon receiving any of the aforementioned redirection reason values, user equipment 504 initiates a series of operations to comply with the network's redirection instructions. User equipment 504 first disables its required 6G mode to prevent immediate re-attempt to reconnect to the 6G network. Subsequently, user equipment 504 switches to the indicated legacy network instead of continuing to attempt a 6G connection.

[0065] After being disabled, user equipment 504 searches for a suitable cell to connect to the system it has been redirected to. If the reason for rejection is "redirection to EPC required," user equipment 504 searches for a cell belonging to 4G base station 522 that can access EPC 560. If the reason is "redirection to 5GC required," user equipment 504 searches for a cell belonging to 5G base station 512 that can access the 5G core network 550. User equipment 504 then performs a core network selection procedure to select a suitable core network for the system it has been redirected to and configures its protocol stack and parameters accordingly for 4G or 5G operation.

[0066] If user equipment 504 cannot find a suitable cell from the redirected system, user equipment 504 can remain camped on the current system that received the rejection message. This fallback mechanism prevents user equipment 504 from entering a network-unconnected state during the search for the redirected network. User equipment 504 remains camped in a limited service state on the 6G network, allowing emergency calls to be made while continuing to search for the redirected network.

[0067] To manage the temporary disabling of 6G mode, user equipment 504 starts timer 532 when 6G capability is disabled according to a redirection instruction. Timer 532 prevents 6G capability from being permanently disabled and allows for periodic reassessment of network conditions. When timer 532 expires, user equipment 504 re-enables 6G mode and can continue to perform appropriate 6G mobility management (xMM) procedures, such as registration or service request procedures. This timer-based mechanism allows user equipment 504 to periodically check whether the conditions leading to redirection have changed, thereby enabling dynamic adaptation to network evolution and changes in service requirements.

[0068] Figure 6 A flowchart 600 illustrates a method for handling a registration process when a user equipment (UE) service is not supported in a next-generation network. This method can be performed by a UE (e.g., UE 504). In operation 602, the UE sends a registration request or service request to the next-generation core network via the next-generation radio access network. In operation 604, the UE receives a rejection message from the next-generation core network indicating that the next-generation service is unavailable to the UE. In operation 606, in response to receiving the rejection message, the UE performs one or more of a set of operations, including: setting an update status to indicate that registration on the next-generation core network associated with the next-generation radio access network is not permitted; deleting a temporary identity associated with the next-generation core network; and deleting the last registration location information associated with the next-generation core network.

[0069] In some implementations, the operation group further includes resetting an attempt counter. This attempt counter includes at least one of a registration attempt counter or a business request attempt counter.

[0070] In some implementations, the operation group further includes entering at least one of a restricted service state, a cellless state, or a public land mobile network search state.

[0071] In some implementations, the operation group further includes disabling the next-generation mode of the public land mobile network associated with the next-generation core network. In some implementations, the user equipment adds the public land mobile network to at least one of an existing prohibition list or a new prohibition list associated with the next-generation mode.

[0072] In some implementations, the user equipment starts and disables a timer associated with the next-generation mode for the public land mobile network. When the timer expires, the user equipment removes the public land mobile network from the disabled or prohibited list associated with the next-generation mode. In some implementations, when the timer expires, the user equipment re-enables the next-generation mode for the public land mobile network and performs the next-generation mobility management process.

[0073] In some implementations, the operating group further includes blocking the selection of at least one of the following during the public land mobile network selection process: a next-generation public land mobile network, an independent non-public network, or a next-generation RAT.

[0074] In some implementations, the next-generation core network includes a 6G core network, the next-generation radio access network includes a 6G radio access network, the update status includes a 6GS update status set to 6U3 roaming not allowed, the temporary identity includes a 6G globally unique temporary identifier, and the last registered location information includes the last access registration tracking area identifier or at least one of the tracking area identifiers in the list.

[0075] Figure 7 A flowchart 700 illustrates a method for handling redirection during the registration process in a next-generation wireless network. This method can be performed by a user equipment (e.g., user equipment 504). In operation 702, the user equipment sends a registration request or service request to the next-generation core network via the next-generation radio access network. In operation 704, the user equipment receives a rejection message from the next-generation core network containing a redirection reason indicating that the user equipment should be redirected to the legacy network. In operation 706, in response to receiving the rejection message with the redirection reason, the user equipment disables next-generation mode. In operation 708, the user equipment searches for a suitable cell connected to the legacy network indicated by the redirection reason.

[0076] In some implementations, the redirection reason includes a first reason value, indicating a need for redirection to the Evolved Packet Core (EPC) when the next-generation core network is unable to provide service to the user equipment in any system other than a 4G network. In some implementations, the redirection reason includes a second reason value, indicating a need for redirection to the 5G core when the next-generation core network is unable to provide service to the user equipment in that next-generation network.

[0077] In some implementations, the user equipment performs a core network selection procedure to select the core network of the legacy network, and the user equipment is redirected to that core network.

[0078] In some implementations, when no suitable cell is found from the legacy network, the user equipment remains camped on the current system that received the rejection message.

[0079] In some implementations, a timer is started when the user device disables the next-generation mode. When the timer expires, the user device re-enables the next-generation mode. In some implementations, when the timer expires, the user device executes the next-generation mobility management process.

[0080] In some implementations, the user equipment includes cellular Internet of Things (CIoT) devices, and the redirection is based on cellular IoT optimizations.

[0081] In some embodiments, the next-generation core network includes a 6G core network, the next-generation radio access network includes a 6G radio access network, and the next-generation mode includes a 6G mode.

[0082] Figure 8 A flowchart 800 illustrates a method for handling registration rejection in a 6G wireless network. This method can be performed by a user equipment (e.g., user equipment 504). In operation 802, the user equipment attempts to register with the 6G core network via the 6G radio access network. In operation 804, the user equipment receives a rejection message from the 6G core network, with a rejection reason value indicating that the user equipment does not support 6G services. In operation 806, the user equipment sets its 6GS update status to 6U3 roaming not allowed. In operation 808, the user equipment deletes its 6G globally unique temporary identifier. In operation 810, the user equipment deletes its last registration location information, including the last access registration tracking area identifier or at least one of the tracking area identifiers. In operation 812, the user equipment disables the 6G mode for the public land mobile network associated with the 6G core network. In operation 814, the user equipment starts a timer associated with disabling the 6G mode. In operation 816, when the timer expires, the user equipment re-enables the 6G mode for the public land mobile network.

[0083] In some embodiments, the user equipment resets at least one of the registration attempt counter or the service request attempt counter. The user equipment enters at least one of the restricted service state, the cellless state, or the public land mobile network search state. In some embodiments, during the public land mobile network selection process, when the 6G mode is disabled for the public land mobile network, the user equipment prevents the selection of at least one of the 6G public land mobile network, the 6G standalone non-public network, or the 6G radio access technology.

[0084] exist Figure 5 As shown and in Figures 6 to 8 User equipment 504 referenced in the flowchart may include... Figure 2Similar hardware components are described in User Equipment 250. Specifically, User Equipment 504 may include one or more antennas 252 for transmitting and receiving radio signals on multiple frequency bands, including traditional 4G / 5G and next-generation 6G frequencies. User Equipment 504 may also include one or more receivers 254RX and transmitters 254TX coupled to the antennas, a receive processor 256 and a transmit processor 268 for implementing physical layer functions, and a channel estimator 258 for deriving channel estimates from reference signals. The controller / processor 259 in User Equipment 504 may be configured to implement the registration process, rejection message processing, and mode management operations described in this specification, including managing 6GS update status, processing temporary identities such as 6G globally unique temporary identifiers, and controlling a timer 532 for managing disabled public terrestrial mobile networks.

[0085] The memory 260 associated with the controller / processor 259 in user equipment 504 can store data for execution. Figure 6 and Figure 7 The program code and data of the method include maintaining a prohibited list for public terrestrial mobile networks / standalone non-public networks, storing last registered location information such as a tracking area identifier list, and tracking next-generation mode enable status. The controller / processor 259 can execute stored instructions to perform various operations, such as deleting a temporary identity, resetting the attempt counter, entering a restricted service state, and managing redirection to a legacy network (5G core or Evolved Packet Core) when a specific reason value is indicated, upon receiving a rejection message with a new reason value from the 6G core network 540. These hardware components enable user equipment 504 to seamlessly switch between next-generation 6G networks and legacy 4G / 5G networks, depending on network support and subscription capabilities, implementing the intelligent fallback mechanism described herein.

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

[0087] The foregoing description is intended to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by 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 should be given the full scope consistent with the language of the claims, wherein references to singular elements do not imply “only one,” but rather “one or more,” unless otherwise specified. The term “exemplary” as used herein means “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 otherwise expressly stated, the term “some” means one or more. Phrases 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, phrases 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 mean 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 elements described in this specification, as long as they are known or will be known in the art by one of ordinary skill 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 exclusive use in the public domain, whether or not it is expressly stated in the claims. The terms "module," "mechanism," "element," "device," etc., should not be considered as substitutes for the word "means." Therefore, unless the phrase "means for..." is expressly used in the claims, no element of a claim should be construed as a means plus a functional element.

Claims

1. A method for wireless communication of a user equipment, comprising: Send registration requests or service requests to the next-generation core network through the next-generation wireless access network; Receive a rejection message from the next-generation core network, indicating that the next-generation service is unavailable to the user equipment. as well as In response to receiving the rejection message, perform one or more operations from an operation group, including: Set the update status to indicate that registration is not allowed on the next-generation core network associated with the next-generation radio access network; Delete temporary identities associated with this next-generation core network; and Delete the last registered location information associated with this next-generation core network.

2. The method of claim 1, wherein the operation group further comprises: Reset the attempt counter, wherein the attempt counter includes at least one of the registration attempt counter or the business request attempt counter.

3. The method of claim 1, wherein the operation group further comprises: Enter at least one of the following states: restricted service, no cell, or public terrestrial mobile network search state.

4. The method of claim 1, wherein the operation group further comprises: Disable the next-generation mode of the public land mobile network associated with this next-generation core network.

5. The method of claim 4, further comprising: Add the public land mobile network to at least one of the existing or new prohibited lists related to the next-generation model.

6. The method of claim 4, further comprising: Enable and disable timers associated with this next-generation mode for the public land mobile network; as well as When the timer expires, the public land mobile network will be removed from the disabled or prohibited list associated with the next-generation mode.

7. The method of claim 6, further comprising: When the timer expires, the next-generation mode for the public land mobile network will be reactivated; as well as Implement next-generation mobility management processes.

8. The method of claim 1, wherein the operation group further comprises: During the public land mobile network selection process, prevent the selection of at least one of the following: next-generation public land mobile network, standalone non-public network, or next-generation RAT.

9. The method of claim 1, wherein: This next-generation core network includes a 6G core network; This next-generation wireless access network includes 6G wireless access network; This update status includes the 6GS update status, which is set to 6U3 roaming not allowed; This temporary identity includes a 6G globally unique temporary identifier; and The last registered location information includes the last access registration tracking area identifier or at least one of the tracking area identifiers in the list.

10. A method for wireless communication of a user equipment, comprising: Send registration requests or service requests to the next-generation core network through the next-generation wireless access network; Receive a rejection message from the next-generation core network, which includes a redirection reason and indicates that the user equipment should be redirected to the legacy network. as well as In response to receiving the rejection message with the reason for the redirection: Disable next-generation mode; and Search for multiple suitable cells for the legacy network connection indicated by the redirection reason.

11. The method of claim 10, wherein the redirection reason includes: When the next-generation core network is unable to provide service to the user equipment in any system other than a 4G network, the first cause value indicates that a redirect to the evolved packet core is required; or When the next-generation core network is unable to provide service to the user equipment in the next-generation network, the second cause value indicates that redirection to the 5G core is required.

12. The method of claim 10, further comprising: The core network selection process is executed to select the core network of the legacy network, and the user equipment is redirected to that core network.

13. The method of claim 10, further comprising: When no suitable cell is found from the traditional network, remain camped on the current system that received the rejection message.

14. The method of claim 10, further comprising: A timer is started when the next-generation mode is disabled; as well as When the timer expires, the next-generation mode will be reactivated.

15. The method of claim 14, further comprising: When the timer expires, execute the next-generation mobility management process.

16. The method of claim 10, wherein the user equipment includes a cellular IoT device, and wherein the redirection is based on cellular IoT optimization.

17. The method of claim 10, wherein: This next-generation core network includes a 6G core network; This next-generation wireless access network includes a 6G wireless access network; and This next-generation model includes a 6G mode.

18. A method for wireless communication of a user equipment, comprising: Attempt to register with the 6G core network via the 6G wireless access network; A rejection message is received from the 6G core network, and the rejection reason value indicates that the user equipment does not support 6G services. Set the 6GS update status to 6U3 roaming not allowed; Delete the 6G globally unique temporary identifier; Delete the last registered location information, which includes the last visited registered tracking region identifier or at least one of the tracking region identifiers in the list. Disable the 6G mode of the public terrestrial mobile network associated with this 6G core network; Start and disable timers associated with this 6G mode; When the timer expires, the 6G mode will be reactivated for the public terrestrial mobile network.

19. The method of claim 18, further comprising: Reset at least one of the registration attempt counter or the service request attempt counter; Entering at least one of the following states: restricted service, no cell, or public land mobile network search.

20. The method of claim 18, further comprising: During the public land mobile network selection process, when the 6G mode is disabled for that public land mobile network, the selection of at least one of the following is prevented: 6G public land mobile network, 6G standalone non-public network, or 6G RAT.

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 registration or service requests to the next-generation core network through the next-generation wireless access network; A rejection message is received from the next-generation core network, indicating that the user equipment is not available with next-generation services; as well as In response to receiving the rejection message, perform one or more operations from the following groups of operations: Set the update status to indicate that registration is not allowed in the next-generation core network associated with this next-generation radio access network; Delete temporary identities associated with this next-generation core network; as well as Delete the last registered location information associated with this next-generation core network.

Images