Wireless communication method and wireless communication device using same
By maintaining the CAG information list in user equipment and performing corresponding operations according to changes in authorized status, the service interruption problem caused by changes in CAG effectiveness in 5GMM is solved, service stability and rapid adaptation are achieved, and the flexibility of 5G mobility management is improved. Sex and reliability.
Patent Information
- Application Number
- CN202410731649.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-06-04
- Filing Date
- 2024-06-06
- Publication Date
- 2024-12-06
AI Technical Summary
In the process of 5G mobility management (5GMM), it is difficult for the prior art to effectively manage the effectiveness changes of closed access groups (CAG), resulting in service interruption or instability of user equipment (UE) when the access authorization status of CAG cells changes.
The user equipment (UE) maintains a data structure containing a list of CAG information that includes a list of allowed CAGs associated with the current public land mobile network (PLMN), through which the authorization status of the CAG ID is determined and executed when the authorization status changes. Corresponding operations, such as aborting the ongoing 5GMM program and releasing the NAS signal connection.
It realizes service stability and rapid adaptation of user equipment when the access authorization status of CAG cell changes, avoids service interruptions caused by CAG ID authorization failure, and improves the flexibility and reliability of 5G mobility management.
Smart Images

Figure CN119095070A_ABST
Abstract
Description
Technical Field
[0001] The present application relates generally to communication systems, and more specifically to the technology of methods and devices for handling 5G mobility management (5GMM) procedures between changes in the validity of closed access groups (CAGs). Background Art
[0002] Unless otherwise indicated herein, the approaches described in this section are not prior art to the following claims and are not admitted to be prior art by inclusion in this section.
[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of these multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0004] These multiple-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a municipal, district, or even global level. One example is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promoted by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements may also apply to other multiple-access technologies and the telecommunication standards that adopt them. Summary of the invention
[0005] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all intended aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that is presented later.
[0006] According to one embodiment, a method, a computer-readable medium and an apparatus are provided. The method can be performed by a user equipment UE. In certain configurations, the UE maintains a closed access group CAG information list containing one entry. The UE supports enhanced CAG information. The entry includes an allowed CAG list associated with a current public land mobile network PLMN. The allowed CAG list includes one or more CAG identifiers ID. The UE accesses the current PLMN through the current CAG cell with the CAG ID. The CAG ID is determined to be authorized based on the allowed CAG list associated with the current PLMN. In response to a first event, the UE performs one or more operations, including: if an ongoing UE-initiated 5G mobility management 5GMM program exists, the ongoing UE-initiated 5GMM program is terminated, and if a non-access layer NAS signal connection exists, the NAS signal connection is released locally.
[0007] To accomplish the foregoing and related ends, the features included in one or more aspects and specifically pointed out in the claims are fully described below. The following description and the accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are indicative of several of the various ways of employing the principles of the various aspects, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 is an example diagram showing a wireless communication system and an access network.
[0009] Figure 2 is an example diagram showing a base station communicating with a user equipment UE in an access network.
[0010] Figure 3 An example logical architecture of a distributed access network is shown.
[0011] Figure 4 Shows an example physical architecture of a distributed access network.
[0012] Figure 5 is an example diagram showing a time slot centered around the downlink.
[0013] Figure 6 is an example diagram showing a time slot centered on the uplink.
[0014] Figure 7 is an example diagram showing a communication system with a public land mobile network PLMN, a specific network SNPN and a PNO-NPN / CAG providing access for local services.
[0015] Figure 8 is an example diagram showing an example procedure for user equipment UE to access a CAG cell.
[0016] Fig. 9 is an example diagram showing a sample CAG information list.
[0017] Fig.10 is a flow chart showing an example procedure of the user equipment UE after the CAG ID becomes unauthorized.
[0018] Fig.11 is a flow chart showing an example procedure of the user equipment UE.
[0019] Fig.12 is a flow chart showing an example procedure of the user equipment UE.
[0020] Fig.13 It is a flow chart showing a method (process) of wireless communication of user equipment UE. DETAILED DESCRIPTION
[0021] The technical terms in this specification are used in the technical field. If there is an explanation or definition of certain technical terms in this specification, the technical terms in this part will take precedence over the explanation or definition elsewhere. The present invention of each embodiment has one or more technical features. Where possible, a person of ordinary skill in the art can selectively implement some or all of the technical features of the present invention, or selectively combine these technical features of the present invention.
[0022] Several aspects of telecommunication systems will now be described with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and depicted in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or a combination of both. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.
[0023] For example, an element, any portion of an element, or any combination of elements may be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, etc., as well as other hardware suitable for performing the various functions described herein. One or more processors in a processing system may execute software. Software should be broadly understood as instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0024] Therefore, in one or more example aspects, the functions described may be implemented in hardware, software, or a combination of the two. If implemented in software, the functions may be stored or encoded as a computer-readable medium on one or more instructions or codes. Computer-readable media include computer storage media. The storage medium may be any available medium that a computer can access. For example, and not limited to, such a computer-readable medium may include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the above types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0025] Figure 1 is a diagram of an example wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, user equipment (UEs) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base stations 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 home cells, micro cells, and micro cells.
[0026] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a backend link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a backend link 184. Among other functions, base stations 102 can perform one or more of the following functions: transmission of user data, 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, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via a backend link 134 (e.g., an X2 interface). The backend link 134 may be wired or wireless.
[0027] Base stations 102 may communicate wirelessly with user equipment (UEs) 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the user equipment (UEs) 104 may include uplink (UL) (also referred to as reverse link) transmissions from the user equipment (UE) 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the user equipment (UE) 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be performed over one or more carriers. The base station 102 / user equipment (UEs) 104 may use spectrum with a bandwidth of up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz), with each carrier allocated in a carrier aggregation of a total of Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent. The allocated carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include one primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).
[0028] Certain user equipments (UEs) 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed via various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.
[0029] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with Wi-Fi stations (STAs) 152 via a communication link 154 to communicate in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, STAs 152 / AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.
[0030] The small base station 102' may operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small base station 102' may adopt NR and use the same 5 GHz unlicensed spectrum as the Wi-Fi AP 150. The small base station 102' adopting NR in the unlicensed spectrum may enhance the coverage and / or increase the capacity of the access network.
[0031] Base station 102, whether a small base station 102' or a large base station (e.g., a macro base station), may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, may communicate with UE 104 in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies. When gNB 180 operates at mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz with wavelengths between 1 mm and 10 mm. Radio waves in this frequency band may be referred to as millimeter waves. Frequencies near mmW may drop to 3 GHz with wavelengths of 100 mm. Super high frequency (SHF) bands are between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz-300 GHz) have extremely high path loss and short range. The mmW base station 180 may use beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
[0032] The base station 180 may transmit one or more beamformed signals in a transmit direction 108a to the UE 104. The UE 104 may receive one or more beamformed signals in a receive direction 108b from the base station 180. The UE 104 may also transmit one or more beamformed signals in a transmit direction to the base station 180. The base station 180 may receive one or more beamformed signals in a receive direction from the UE 104. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for the base station 180 / UE 104. The transmit and receive directions of the base station 180 may be the same or different. The transmit and receive directions of the UE 104 may be the same or different.
[0033] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signals between the UEs 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide configuration and delivery functions for MBMS user services. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and start MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcast by a specific service, and may be responsible for session management (start / stop) and collecting eMBMS related billing information.
[0034] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a location management function (LMF) 198, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signals between the UEs 104 and the core network 190. Typically, the SMF 194 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to the IP services 197. The IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.
[0035] Base stations may also be referred to as gNBs, Node Bs, evolved Node Bs (eNBs), access points, base transceiver stations, wireless base stations, wireless transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmission reception points (TRPs), or other appropriate terms. Base stations 102 provide access points for UEs 104 to enter EPC 160 or core network 190. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a site, a mobile site, a subscription site, a mobile unit, a subscription unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscription site, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a user agent, a mobile client, a client, or other appropriate terminology.
[0036] Although the present disclosure may refer to the fifth generation new radio (5G New Radio, referred to as NR), the present disclosure may also be applicable to other similar fields, such as Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM) or other wireless / radio access technologies.
[0037] Figure 22 is a block diagram of a base station 210 communicating with a user equipment (UE) 250 in an access network. In the downlink (DL), IP packets from the evolved core network (EPC) 160 may be provided to the controller / processor 275. The controller / processor 275 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 275 provides RRC layer functions associated with system information (e.g., MIB, SIBs) broadcasting, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), measurement configuration for cross-radio access technology (RAT) mobility, and UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel priority.
[0038] The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 216 processes the mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 274 may be used to determine coding and modulation schemes, as well as to perform spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 250. Each spatial stream may then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX may modulate an RF carrier for transmission with a corresponding spatial stream.
[0039] At the UE 250, each receiver 254RX receives a signal through its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functions associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams intended for the UE 250. If there are multiple spatial streams intended for the UE 250, they may be combined into a single OFDM symbol stream by the RX processor 256. The RX processor 256 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. By determining the most likely signal constellation point transmitted by the base station 210, the symbols and reference signals on each subcarrier are recovered and demodulated. These soft decisions may be based on channel estimates calculated by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 210. The data and control signals are then provided to the controller / processor 259 which implements Layer 3 and Layer 2 functions.
[0040] The controller / processor 259 may be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer readable medium. In the uplink (UL), the controller / processor 259 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 259 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0041] Similar to the functional description associated with DL transmission of the base station 210, the controller / processor 259 provides RRC layer functions associated with system information (e.g., MIB, SIBs) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, connection, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel priority.
[0042] Channel estimates derived by the channel estimator 258 from a reference signal or feedback transmitted by the base station 210 may be used by the TX processor 268 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antennas 252 via separate transmitters 254TX. Each transmitter 254TX may modulate an RF carrier with a corresponding spatial stream for transmission. The UL transmission is processed at the base station 210 in a manner similar to the receiver function described at the UE 250. Each receiver 218RX receives a 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.
[0043] The controller / processor 275 may be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer readable medium. In the uplink (UL), the controller / processor 275 provides demultiplexing between transports and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the user equipment (UE) 250. The IP packets from the controller / processor 275 may be provided to the EPC 160. The controller / processor 275 is also responsible for error detection using an acknowledgement (ACK) and / or negative acknowledgement (NACK) protocol to support hybrid automatic repeat request (HARQ) operations.
[0044] New Radio (NR) may refer to a radio configured to operate according to a new air interface (e.g., a non-orthogonal frequency division multiple access (OFDMA) based air interface) or a fixed transport layer (e.g., non-Internet Protocol (IP)). NR may use orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) in uplink and downlink, and may include support for half-duplex operation using time division duplex (TDD). NR may include enhanced mobile broadband (eMBB) services for wide bandwidths (e.g., over 80 MHz), millimeter wave (mmW) for high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) for non-backward compatible machine type communication (MTC) technologies, and / or mission critical services for ultra-reliable low latency communication (URLLC) services.
[0045] A single component carrier bandwidth may support 100MHz. In one example, NR resource blocks (RBs) may span 12 subcarriers with a subcarrier bandwidth of 60kHz and a duration of 0.25ms, or a bandwidth of 30kHz and a duration of 0.5ms (similarly, for 15kHz SCS, a 50MHz BW duration of 1ms). Each radio frame may consist of 10 subframes (10, 20, 40, or 80 NR time slots) and be 10ms in length. Each time slot may indicate the link direction (i.e., downlink (DL) or uplink (UL)) for data transmission, and the link direction of each time slot may be switched dynamically. Each time slot may include DL / UL data as well as DL / UL control data. The UL and DL time slots of NR may be as described below with respect to Figure 5 and Figure 6 Describe in more detail.
[0046] The NR RAN may include a central unit (CU) and distributed units (DUs). An NR base station (e.g., gNB, 5GNode B, Node B, transmission reception point (TRP), access point (AP)) may 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., the central unit or the distributed unit) can configure the cell. DCells may be cells for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or handover. In some cases, DCells may not transmit synchronization signals (SS), and in some cases DCells may transmit SS. The NR base station may transmit a downlink signal to the UE indicating the cell type. Based on the cell type indication, the UE may communicate with the NR base station. For example, the UE may determine the NR base station to be considered for cell selection, access, handover, and / or measurement based on the indicated cell type.
[0047] Figure 3 An example logical architecture of a distributed RAN 300 is shown, in accordance with aspects of the present document. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be the central unit (CU) of the distributed RAN. The backend interface to the next generation core network (NG-CN) 304 may terminate at the ANC. The backend interface to adjacent next generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as base stations, NR base stations, Node Bs, 5G NBs, APs or other terms). As mentioned above, TRP may be used interchangeably with "cell".
[0048] TRPs 308 may be a distributed unit (DU). TRPs may be connected to one ANC (ANC 302) or multiple ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, the TRP may be connected to multiple ANCs. The TRP may include one or more antenna ports. TRPs may be configured to serve UEs individually (e.g., dynamically selected) or together (e.g., joint transmission).
[0049] The local architecture of the distributed RAN 300 may be used to illustrate the fronthaul definition. The architecture may be defined to support fronthaul solutions across different deployment types. For example, the architecture may be based on transport network capabilities (e.g., bandwidth, latency and / or jitter). The architecture may share features and / or components with LTE. According to aspects, the next generation AN (NG-AN) 310 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.
[0050] The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be provisioned within a TRP and / or between TRPs via the ANC 302. Depending on aspects, an interface between TRPs may not be required / existent.
[0051] According to aspects, there may be dynamic configuration of split logical functions in the architecture of the distributed RAN 300. PDCP, RLC, MAC protocols may be adaptively placed in the ANC or TRP.
[0052] Figure 4 An example physical architecture of a distributed RAN 400 is shown, in accordance with aspects of the present document. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU may be centrally deployed. C-CU functions may be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity. A centralized RAN unit (C-RU) 404 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have a distributed deployment. The C-RU may be closer to the edge of the network. A distribution unit (DU) 406 may host one or more TRPs. The DU may be located at the edge of the network with radio frequency (RF) functions
[0053] Figure 5 500, illustrating an example of a downlink (DL)-centric timeslot. The downlink-centric timeslot may include a control portion 502. The control portion 502 may be present at an initial or beginning portion of the downlink-centric timeslot. The control portion 502 may include various scheduling information and / or control information corresponding to various portions of the downlink-centric timeslot. In some configurations, the control portion 502 may be a physical downlink control channel (PDCCH), such as Figure 5 As shown. The downlink-centric time slot may also include a downlink data portion 504. The downlink data portion 504 may sometimes be referred to as the payload of the downlink-centric time slot. The downlink data portion 504 may include communication resources for communicating downlink data from a scheduling entity (e.g., a UE or a BS) to a subordinate entity (e.g., a UE). In some configurations, the downlink data portion 504 may be a physical downlink shared channel (PDSCH).
[0054] The downlink-centric time slot may also include a common uplink (UL) portion 506. The common uplink portion 506 may sometimes be referred to as an uplink burst, a common uplink burst, and / or other appropriate terms. The common uplink portion 506 may include feedback information corresponding to various portions of the downlink-centric time slot. For example, the common uplink portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and / or various other appropriate types of information. The common uplink portion 506 may include additional or alternative information, such as information related to a random access channel (RACH) procedure, scheduling requests (SRs), and various other appropriate types of information.
[0055] like Figure 5 As shown, the end of the downlink data portion 504 may be separated in time from the beginning of the common uplink portion 506. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or other appropriate terms. This separation provides time for switching from downlink communications (e.g., reception operations by a subordinate entity (e.g., a UE)) to uplink communications (e.g., transmissions by a subordinate entity (e.g., a UE)). Those of ordinary skill in the art will appreciate that the above is merely an example of a downlink-centric time slot, and that alternative structures with similar features may exist without necessarily departing from the aspects described herein.
[0056] Figure 6 600, illustrating an example uplink (UL) centric timeslot. The uplink centric timeslot may include a control portion 602. The control portion 602 may be present at the beginning or start of the uplink centric timeslot. Figure 6 The control portion 602 in the above reference may be Figure 5 The control portion 502 is similar. The uplink-centric time slot may also include an uplink data portion 604. The uplink data portion 604 may sometimes be referred to as the payload of the uplink-centric time slot. The uplink portion may refer to the communication resources used to communicate uplink data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion 602 may be a physical downlink control channel (PDCCH).
[0057] like Figure 6As shown, the end of the control portion 602 may be separated in time from the beginning of the uplink data portion 604. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or other appropriate terms. This separation provides time for switching from downlink communications (e.g., reception operations by a scheduling entity) to uplink communications (e.g., transmissions by a scheduling entity). The uplink-centric timeslot may also include a common uplink portion 606. Figure 6 The common uplink portion 606 in the above reference may be the same as Figure 5 The common uplink portion 506 is similar. The common uplink portion 606 may also include information related to a channel quality indicator (CQI), a sounding reference signal (SRSs), and various other suitable types of information. It will be appreciated by those skilled in the art that the above is merely an example of an uplink-centric timeslot, and that alternative structures with similar features may exist without necessarily departing from the aspects described herein.
[0058] In some cases, two or more slave entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications for such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, Internet of Things (IoT) communications, mission-critical mesh networks, and / or various other appropriate applications. Generally, a sidelink signal may refer to a signal communication from one slave entity (e.g., UE1) to another slave entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may use licensed spectrum for communication (unlike wireless local area networks that typically use unlicensed spectrum).
[0059] A Public Land Mobile Network (PLMN) is a network established and operated by an administration or recognized operating organization (ROA) with the specific purpose of providing land mobile communication services to the public. PLMN provides communication possibilities for mobile users. PLMN may provide services in one or more frequency band combinations. Access to PLMN services is achieved through an air interface involving radio communications between mobile phones and base stations with integrated IP network services. A PLMN may include multiple radio access networks (RANs) using different radio access technologies (RATs) to access mobile services. The radio access network is a part of a mobile communication system that implements radio access technologies. Conceptually, the RAN sits between mobile devices and provides connectivity to their core network (CN). According to the standards, mobile phones and other wirelessly connected devices are referred to as user equipment (UE, i.e. MS), terminal equipment (TE), mobile station (MS, i.e. UE), mobile terminal (MT), etc. Examples of different RATs include 2G GERAN (GSM) radio access network, 3G UTRAN (UMTS) radio access network, 4G E-UTRAN (LTE), 5G New Radio (NR) radio access network, Next Generation RAN (NG-RAN), and other non-3GPP access RATs, including WiFi.
[0060] In contrast to PLMN, a non-public network (NPN) is a network used for non-public purposes. An NPN is either a standalone non-public network (SNPN), which is operated by an NPN operator and does not rely on network functions provided by the PLMN; or a public network integrated NPN (PNI-NPN), which is a non-public network deployed with the support of a PLMN. Access to a SNPN can be individually authenticated and authorized by a credential holder (CH). The combination of a PLMN ID and a network identifier (NID) identifies a SNPN. A UE may be enabled for a SNPN.
[0061] A PNI-NPN is an NPN provided over a PLMN, for example, over a dedicated DNN or one or more network slice instances assigned to the NPN. When a PNI-NPN is provided over a PLMN, the UE shall have a subscription to the PLMN to access the PNI-NPN. Since network slicing cannot prevent a UE from attempting to access the network in an area where the UE is not allowed to use the network slice assigned to the NPN, access control for the PNI-NPN can be applied using a closed access group. A closed access group (CAG) identifies a group of subscribers that are allowed to access one or more CAG cells associated with the CAG. A CAG is used for a PNI-NPN to prevent a UE that is not allowed to access the NPN over an associated cell from automatically selecting and accessing the associated CAG cell. The CAG is used for access control, for example, authorization at the time of cell selection and is configured in a subscription as part of mobility restrictions. The CAG is identified by a CAG identifier, which is unique within the scope of the PLMN ID.
[0062] Local or localized services are services that are provided in a specific / limited area and / or are limited in time (specific time period). Localized service providers are application providers or network operators who localize their services and provide services to end users over a hosted network. The hosted network is the network that provides access to localized services and can be a SNPN or PNI-NPN, while the home network is the network that has the subscription or credentials currently used by the UE. The home network can be a Home-PLMN or Subscribed-SNPN. The end user can enable or disable access to localized services. If the end user disables access to localized services, the UE (i.e. MS) may not be able to access the NPN that provides access to localized services.
[0063] In order to provide (access) local services to UEs, the UE needs to be able to discover, select and access an NPN (as a hosting network) that provides local service access.
[0064] Figure 7 is a schematic diagram showing a communication system 700 having a PLMN 710, a SNPN 720, and a public network integrated NPN (PNI-NPN) / CAG 730 providing local service access. Figure 7 As shown, the PLMN network 710 includes control plane functions, user plane functions (e.g., UPF), and applications that provide various services by communicating with multiple user equipments (UEs) including UE 701. A serving base station (e.g., gNB) 712 is part of a radio access network (RAN) 740. The RAN 740 provides radio access to the UE 701 via a radio access technology (RAT). An access and mobility management function (AMF) in the PLMN 710 communicates with the gNB 712. The UE 701 may be equipped with one or more radio frequency (RF) transceivers.
[0065] The SNPN network 720 includes control plane functions, user plane functions (e.g., UPF), and applications that provide various services by communicating with multiple UEs including UE 701. A combination of a PLMN ID and a network identifier (NID) identifies a SNPN. A serving base station (e.g., gNB) 722 is part of a radio access network (RAN) 750. The RAN 750 provides radio access to the UE 701 via a radio access technology (RAT). The AMF in the SNPN 720 communicates with the gNB 722. The SNPN 720 is operated by an NPN operator and does not rely on network functions provided by the public network. Access to the SNPN can be authenticated and authorized individually by a credential holder (CH). The NG-RAN node that provides access to the SNPN broadcasts the following information: one or more PLMN IDs, and a list of NIDs (723) for each PLMN ID that identifies the non-public networks to which the NG-RAN provides access. A UE supporting SNPN is configured with a PLMNID and NID (SNPN ID) for subscribing to SNPN, and a UE supporting SNPN that supports accessing SNPN using credentials from a credential holder may also be configured with information for SNPN selection (SNPN selection information or configuration) and registration using SNPN subscription or using PLMN subscription (USIM) (in SNPN access mode) (702).
[0066] The PNI-NPN (CAG) network 730 includes a control plane function (optional, as it may rely on the control plane function of the PLMN), a user plane function (optional, as it may rely on the user plane function of the PLMN), and an application that provides various services by communicating with multiple UEs including UE 701. The PNI-NPN (CAG) 730 is a non-public network that is supported by a PLMN, such as PLMN 710, by sharing, for example, RAN / gNB 712 and, for example, control plane functions. A CAG identifies a group of subscribers that are allowed to access one or more CAG cells associated with the CAG. The CAG is used in the PNI-NPN to prevent UEs that are not allowed to access the NPN through the associated cell from automatically selecting and accessing the associated CAG cell. The CAG is identified by a CAG identifier that is unique within the range of PLMN IDs. The CAG cell broadcasts one or more CAG identifiers (113) for each PLMN, and the UE is configured with CAG-related configuration / information (e.g., an (enhanced) CAG information list containing a list of CAGs allowed for each PLMN) (702).
[0067] Local or localized services are services that are provided in a specific / limited area and / or are limited in time (specific time period). Localized service providers are application providers or network operators who localize their services and provide services to end users through a hosted network. The hosted network is the network that provides access to localized services and can be a SNPN or PNI-NPN, while the home network is the network that has the subscription or credentials currently used by the UE. Figure 7 In the example of FIG. 5 , both SNPN 720 and PNI-NPN (CAG) 730 may be managed networks that provide local service access.
[0068] When the localized service in the network is completed, it is expected that all user equipment (UE) registered with the network will be moved to other networks or other cells in the same network. The other network can be a HPLMN, a VPLMN or another SNPN. The user equipment (UE) may stop using network resources for localized services for a variety of reasons, such as: (a) the localized service in the network has been completed; (b) the validity conditions selected by the network are no longer met; (c) the user decides to stop using before the localized service is completed (for example, the end user disables access to the localized service); or (d) the network makes a policy decision that causes the user equipment (UE) to be deregistered before the localized service is completed. Validity information or restrictions or criteria or conditions (703) are provided or configured to the user equipment (UE) as part of the localized service information to restrict the user equipment (UE) from accessing the SNPN / PNI-NPN (as a hosting network) that provides the localized service. In order to provide localized services to the user equipment (UE), the user equipment (UE) needs to be able to discover, select and access the SNPN / PNI-NPN (as a hosting network) that provides the localized service. The discovery mechanism is based on providing or configuring the User Equipment (UE) with appropriate information.
[0069] Figure 8 8 is a diagram of an example process 800, showing interactive communications between a user equipment (UE) and a base station. Specifically, the user equipment (UE) 810 may be a user equipment (UE) supporting CAG (e.g., user equipment (UE) 701), and the user equipment (UE) 810 may be pre-configured (or reconfigured) with corresponding CAG information by the base station 820, so as to use CAG, i.e., access the PLMN through the CAG cell 830.
[0070] like Figure 8As shown, when the user equipment (UE) 810 registers with the base station 820, the base station 820 of the PLMN sends the CAG-related configuration to the user equipment (UE) 810 through a message 840. After receiving the message 840, the user equipment (UE) 810 may store the CAG-related configuration in the message 840 so that the user equipment (UE) 810 can access the corresponding PLMN through the CAG cell supporting the CAG ID later. In some configurations, the message 840 may include a CAG information list, which includes zero, one or more entries, each entry including: (a) a PLMN ID indicating the corresponding PLMN; (b) an allowed CAG list including zero, one or more CAG IDs; and (c) an optional CAG-only indication. The optional CAG-only indication (also referred to as an indication of "indicating that the MS is only allowed to access the 5GS through the CAG cell") is an indication that the user equipment (UE) 810 is only allowed to access the 5GS (i.e., PLMN) through the CAG cell (e.g., the CAG cell 830). In certain configurations, the CAG information list provided by the network is stored in a non-volatile memory of the user equipment (UE) 810 .
[0071] In certain configurations, for each entry in the CAG information list, the CAG ID in the allowed CAG list may include or be associated with additional standard information. Examples of standard information may include at least one of the following: time criteria, location criteria, and other criteria. For example, the CAG ID may be configured with time validity information to indicate the time criteria (e.g., an authorized time period). In this case, when the time criteria indicated by the time validity information is met (e.g., the current time of the user equipment (UE) 810 matches the authorized time period indicated by the time validity information), the CAG ID may be deemed to be authorized, and when the time criteria is no longer met (e.g., the current time does not match the authorized time period), the CAG ID is not authorized.
[0072] Fig. 9 is a diagram of an example CAG information list. Fig. 9As shown, the CAG information list 900 includes 3 entries, each of which includes a corresponding PLMN ID 910 and an allowed CAG list 920. For entry 1, the corresponding PLMN ID 910 indicates PLMN 111, and the allowed CAG list 920 includes 3 CAG IDs, including CAG 11, CAG 12, and CAG 13. For entry 2, the corresponding PLMN ID 910 indicates PLMN 222, and the allowed CAG list 920 includes 2 CAG IDs, including CAG 21 and CAG 22. In addition, entry 2 also includes a CAG-only indication 930 (i.e., an indication indicating that the user equipment (UE) is only allowed to access the 5GS through the CAG cell). For entry 3, the corresponding PLMN ID 910 indicates PLMN 333, and the allowed CAG list 920 includes 2 CAG IDs, including CAG 31 and CAG 32. In addition, the allowed CAG list 920 of entry 3 is an enhanced allowed CAG list, in which each CAG ID may have corresponding time validity information. In other words, the user equipment UE storing the CAG information list 900, including the enhanced allowed CAG list 920, supports enhanced CAG information. For example, CAG 31 is configured with time validity information, indicating that the authorized time period is from 10:00 on January 1 to 12:00 on January 1, indicating that the user equipment UE can access PLMN 333 through the CAG cell supporting CAG 31 during this authorized time period (10:00 on January 1 to 12:00 on January 1). Similarly, CAG 32 is configured with time validity information, indicating that the authorized time period is from 14:00 on January 1 to 16:00 on January 1, indicating that the user equipment UE can access PLMN 333 through the CAG cell supporting CAG 32 during this authorized time period (14:00 on January 1 to 16:00 on January 1).
[0073] refer to Figure 8 , assuming that the CAG-related configuration in message 840 includes the following Fig. 9810 ). The CAG information list 900 is shown, which includes entry 3 of a CAG ID with time validity information (i.e., UE 810 supports enhanced CAG information). In operation 850, a CAG cell 830 supporting one or two CAG IDs within PLMN 333 broadcasts CAG ID 865, including CAG 31 and CAG 32. When the current time of UE 810 matches the authorized time period of CAG 31 (e.g., January 1 at 10:00), in operation 870, UE 810 may begin accessing PLMN 333 through CAG cell 730 with CAG 31. The access may continue during the authorized time period, for example, from 10:00 to 12:00 on January 1. In one embodiment, UE 810 may set a timer for the authorized time period so that UE 810 knows the end of the authorized time period when the timer expires. In another embodiment, based on the allowed CAG list, CAG 31 becomes unauthorized (e.g., the time validity information no longer matches the current time of the UE). In operation 880, after the authorized time period (eg, January 1, 12:01), the UE 810 may perform a corresponding operation because the time standard of CAG 31 is no longer met.
[0074] Fig.10 is a flow chart showing an example procedure of a UE after a CAG ID becomes unauthorized. The procedure 1000 may be performed by a UE (e.g., UE 701 or UE 810) that has stored (e.g., previously received) a CAG information list (e.g., CAG information list 900). When the UE maintains a CAG information list of an allowed CAG list associated with a current PLMN, and the allowed CAG list includes a CAG ID, in operation 1010, when it is determined that the CAG ID is authorized (e.g., the current time of the UE matches the time period indicated by the time validity information of the CAG ID), the UE may access the current PLMN through the CAG ID of the current CAG cell. For example, the UE may selectively set a timer based on the time validity information. The timer is used for the UE to know when the authorized time period indicated by the time validity information expires. After the timer is set, the UE may start to access the PLMN through the CAG ID of the CAG cell, and when the time expires, the UE knows that the time criteria of the CAG ID are no longer met, that is, the CAG ID becomes unauthorized. In operation 1020, the UE determines whether the UE becomes unauthorized (eg, whether the timer expires). If the UE is still authorized (eg, the timer has not expired), the UE may return to operation 1020 to continue monitoring the authorization status.
[0075] When the UE becomes unauthorized (e.g., the timer expires), the UE determines whether the current CAG cell supports at least one CAG ID authorized in the CAG information list based on the allowed CAG list of the current PLMN in operation 1030. If the UE determines that the current CAG cell supports at least one CAG ID authorized in the CAG information list based on the allowed CAG list of the current PLMN, in operation 1040, the UE may continue to access the PLMN through the same CAG cell with this new CAG ID.
[0076] On the other hand, if the UE determines that the CAG ID supported by the current CAG cell is not currently authorized in the CAG information list based on the allowed CAG list of the current PLMN, in operation 1050, the UE determines whether the entry in the CAG information list includes a CAG-only indication, i.e., indicating that the UE is only allowed to access the 5GS (i.e., PLMN) through the CAG cell. If the CAG information list does not include the CAG-only indication, the UE determines that the first event has occurred and the UE can access the PLMN through the CAG cell and the non-CAG cell. In this case, the first event occurs when (1) the CAG ID becomes unauthorized based on the allowed CAG list, (2) the CAG ID supported by the current CAG cell is not currently authorized in the CAG information list based on the allowed CAG list of the current PLMN, and (3) the entry in the CAG information list does not include the CAG-only indication.
[0077] In response to the first event, in operation 1055, the UE performs one or more actions and enters a limited service state, for example, state (5GMM-(DE)REGISTERED.)LIMITED-SERVICE, to search for a suitable CAG or non-CAG cell. Specifically, the actions in response to the first event may include: if there is an ongoing UE-initiated 5GMM procedure, terminating the ongoing UE-initiated 5GMM procedure; if there is an ongoing UE-initiated 5GMM procedure, terminating the ongoing UE-initiated 5GSM procedure; and if there is a NAS signal connection and / or an N1 NAS signal connection, locally releasing the NAS signal connection and / or starting timer T3540 to release the N1 NAS signal connection. In some embodiments, the suitable cell may be a non-CAG cell, or may be another CAG cell that broadcasts the CAGID included in the UE's CAG information list. Once the UE finds a suitable cell, the UE may continue to access the PLMN through the suitable cell.
[0078] If the entry of the CAG information list contains a CAG-only indication, the UE determines that it can only access the current PLMN through a CAG cell and cannot access the same current PLMN through a non-CAG cell. In operation 1060, the UE determines whether there are other CAG IDs that are authorized in the CAG information list based on the allowed CAG list of the current PLMN. If there is a new CAG ID, it may not be supported by the same CAG cell, which means that the UE may have to find a new CAG cell that supports the new CAG ID. If the UE determines that one or more CAG IDs are authorized in the CAG information list based on the allowed CAG list of the current PLMN, the UE also determines that a first event occurs. In this case, the first event occurs when: (1) the CAG ID becomes unauthorized based on the allowed CAG list; (2) the CAG ID supported by the current CAG cell is currently not authorized in the CAG information list based on the allowed CAG list of the current PLMN; (3) the entry of the CAG information list contains a CAG-only indication; (4) one or more CAG IDs are authorized in the CAG information list based on the allowed CAG list of the current PLMN. In operation 1065, the UE performs one or more actions and enters a limited service state, for example, state (5GMM-(DE)REGISTERED.)LIMITED-SERVICE, to search for a suitable CAG cell that supports the new CAG ID. Specifically, the actions in response to the first event may include: if there is an ongoing UE-initiated 5GMM procedure, terminating the ongoing UE-initiated 5GMM procedure; if there is an ongoing UE-initiated 5GSM procedure, terminating the ongoing UE-initiated 5GMM procedure; and if there is a NAS signal connection and / or an N1 NAS signal connection, locally releasing the NAS signal connection and / or starting timer T3540 to release the N1 NAS signal connection.
[0079] On the other hand, the UE may determine that no (other) CAG ID is authorized in the CAG information list based on the allowed CAG list of the current PLMN. For example, the entries of the CAG information list of the current PLMN may not include other CAG IDs. Alternatively, the entries of the CAG information list of the current PLMN may include other CAG IDs, but each CAG ID in the entry is not authorized (for example, each CAG ID is configured with corresponding time validity information, indicating a corresponding authorized time period, and the current time does not match the corresponding authorized time period). In this case, in operation 1070, the UE may determine whether the UE has an emergency PDU session. If the UE does not have an emergency PDU session, the UE cannot stay in the PLMN. In this case, the UE also determines that the first event occurs when: (1) the CAG ID becomes unauthorized based on the allowed CAG list; (2) the CAG ID supported by the current CAG cell is not currently authorized in the CAG information list based on the allowed CAG list of the current PLMN; (3) the entry of the CAG information list contains a CAG-only indication; (4) no CAG ID is authorized in the CAG information list based on the allowed CAG list of the current PLMN; (5) the UE has no emergency PDU session. In operation 1080, the UE may perform one or more actions and enter a PLMN search state, such as state (5GMM-(DE)REGISTERED.)PLMN-SEARCH, and apply a network selection procedure (e.g., a PLMN selection procedure) to search for another network or another PLMN. Specifically, the actions in response to the first event may include: if there is an ongoing UE-initiated 5GMM procedure, terminating the ongoing UE-initiated 5GMM procedure; if there is an ongoing UE-initiated 5GSM procedure, terminating the ongoing UE-initiated 5GMM procedure; and if there is a NAS signal connection and / or N1 NAS signal connection, locally releasing the NAS signal connection and / or starting timer T3540 to release the N1 NAS signal connection.
[0080] On the other hand, if the UE has an emergency PDU session, the UE can stay in the PLMN using the emergency PDU session. In this case, the UE determines that the second event occurs when: (1) the CAG ID becomes unauthorized based on the allowed CAG list; (2) the CAG ID supported by the current CAG cell is currently not authorized in the CAG information list based on the allowed CAG list of the current PLMN; (3) the entry of the CAG information list contains a CAG-only indication; (4) no CAG ID is authorized in the CAG information list based on the allowed CAG list of the current PLMN; (5) the UE has an emergency PDU session. In operation 1090, the UE may perform one or more actions and enter a limited service state for the emergency PDU session, for example, state (5GMM-(DE)REGISTERED.)LIMITED-SERVICE. Specifically, the actions in response to the second event may include: if there is an ongoing UE-initiated 5GMM procedure, terminating the ongoing UE-initiated 5GMM procedure; if there is an ongoing UE-initiated 5GSM procedure, terminating the ongoing UE-initiated 5GMM procedure. In some embodiments, the UE may also locally release all PDU sessions associated with the 3GPP access except for emergency PDU sessions.
[0081] Fig.11is a flow chart of an example procedure for a user equipment UE. The example procedure can be executed by a user equipment (e.g., UE 701) to provide a solution for the CAG / PNI-NPN 5GSM part. At operation 1110, the user equipment receives a downlink NAS transfer message. At operation 1120, after receiving the downlink NAS transfer message, the user equipment checks whether a third event occurs. An example of a third event may include: the payload container type IE is set to "N1 SM information" and the 5GMM cause IE is set to cause #76 "This CAG is not authorized or only CAG cells are authorized". At operation 1130, in response to the third event, the user equipment performs one or more actions, including: passing an indication that the 5GSM message was not forwarded (together with the 5GSM message from the payload container IE of the downlink NAS transport message) to the 5GSM sublayer, setting the 5GS update status to 5U3 Roaming Not Allowed, deleting any 5G-GUTI, deleting the last visited registered tracking area identifier (TAI), deleting the TAI list, deleting the ngKSI, deleting the equivalent PLMN list (if available), entering the PLMN-search state and performing PLMN selection, and entering the limited service state and performing cell (re)selection. If the message has been successfully integrity checked by NAS, the user equipment can set the PLMN-specific attempt counter for the 3GPP access and the PLMN-specific attempt counter for the non-3GPP access for the current SNPN to a maximum value specific to the user equipment implementation. If the message has been successfully integrity checked by NAS and the user equipment also supports registration procedures for the same PLMN through other accesses, the user equipment will also process the 5GMM parameters and 5GMM status of this access as described by the 5GMM cause value.
[0082] Fig.12is a flowchart of an example procedure for a user device. The example procedure can be executed by a user device (e.g., UE701) to provide a solution for the CAG / PNI-NPN 5GSM part. At operation 1210, the user device requests a PDU session related procedure. In some embodiments, the procedure may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure. At operation 1220, the user device may encounter a fourth event during the PDU session related procedure, where an abnormal situation occurs. Examples of the fourth event may include, but are not limited to, receiving an indication that a 5GSM message was not forwarded because this CAG is not authorized or only CAG cells are authorized (together with a PDU session establishment / modification / release request message), and the PDU session ID IE is set to the same value as the PDU session ID sent by the user device. At operation 1230, in response to the fourth event, the user equipment performs one or more actions, including: stopping corresponding timers (e.g., timer T3580 in the PDU session establishment procedure, timer T3581 in the PDU session modification procedure, timer T3582 in the PDU session release procedure), terminating PDU session-related procedures, locally releasing all non-emergency PDUs (and in the PDU session release procedure, locally releasing the PDU session), and not triggering a 5GSM procedure unless the procedure is related to an emergency (until the user equipment deregisters from the SNPN) in the current SNPN.
[0083] Fig.13 It is a flowchart of a method (process) for wireless communication of a user equipment. The method can be performed by a user equipment (e.g., UE 701 or UE 810). At operation 1310, the user equipment maintains a CAG information list containing entries. The user equipment supports enhanced CAG information. The entry includes an allowed CAG list associated with the current PLMN. The allowed CAG list includes one or more CAG IDs. At operation 1320, the user equipment accesses the current PLMN through the current CAG cell with the CAG ID. The CAGID is determined to be authorized based on the allowed CAG list associated with the current PLMN. At operation 1330, in response to the first event, the user equipment performs one or more actions, including: if an ongoing UE-initiated 5GMM procedure exists, terminating the ongoing UE-initiated 5GMM procedure, and if a NAS signal connection exists, locally releasing the NAS signal connection.
[0084] In certain configurations, the first event includes determining that the CAG ID becomes unauthorized based on an allowed CAG list, determining that a CAG ID supported by a current CAG cell is unauthorized in a CAG information list based on an allowed CAG list of a current PLMN, and determining whether the entry includes an indication indicating that the user equipment is only allowed to access the 5GS through the CAG cell.
[0085] In one embodiment, the first event includes: determining that the entry does not include an indication that the user equipment is only allowed to access the 5GS through the CAG cell.
[0086] In one embodiment, the first event includes: determining that the entry includes an indication indicating that the user equipment is only allowed to access the 5GS through the CAG cell, and one or more CAG IDs are authorized in the CAG information list based on the allowed CAG list of the current PLMN.
[0087] In one embodiment, the first event includes: determining that the entry includes an indication that the user equipment is only allowed to access the 5GS through the CAG cell, and no CAG ID is authorized in the CAG information list based on the allowed CAG list of the current PLMN, and determining that the user equipment has no emergency packet data unit (PDU) session.
[0088] In certain configurations, in response to a second event, if an ongoing UE-initiated 5GMM procedure exists, the user equipment aborts the ongoing UE-initiated 5GMM procedure. The second event includes: determining that the CAG ID becomes unauthorized based on an allowed CAG list, determining that a CAG ID supported by a current CAG cell is currently not authorized in a CAG information list based on an allowed CAG list of a current PLMN, determining that an entry includes an indication that the user equipment is only allowed to access a fifth generation system (5GS) through a CAG cell and no CAG ID is authorized in the CAG information list based on an allowed CAG list of a current PLMN, and determining that the user equipment has an emergency PDU session.
[0089] In certain configurations, the CAG ID is configured with time validity information in the allowed CAG list, indicating a time period, and when the current time of the user device matches the time period, the CAG ID is determined to be authorized, and when the current time of the user device does not match the time period, it is determined to be unauthorized based on the allowed CAG list.
[0090] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims present the elements of the various blocks in an example order and are not intended to be limited to the specific order or hierarchy presented.
[0091] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but should be given a full scope consistent with the claims text, wherein unless explicitly stated, the reference to the elements in the singular form is not intended to represent "one and only one", but to represent "one or more". The word "exemplary" is used herein to represent "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or advantageous over other aspects. Unless otherwise explicitly stated, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. Specifically, phrases such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects of the description of the present invention that are known or will later be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is expressly recited in the claims, nothing disclosed herein is intended to be dedicated to the public. The terms "module," "mechanism," "element," "device," and the like may not replace the term "device." Therefore, unless a claim element is expressly recited using the phrase "device for...", no claim element should be interpreted as a device plus function.
Claims
1. A wireless communication method for a user equipment UE, comprising: Maintaining a closed access group CAG information list including an entry, wherein the UE supports enhanced CAG information, the entry including an allowed CAG list associated with a current public land mobile network (PLMN), and the allowed CAG list including one or more CAG identifiers ID; accessing the current PLMN via a current CAG cell having a CAG ID, wherein the CAG ID is determined to be authorized based on the allowed CAG list associated with the current PLMN; as well as In response to a first event, performing one or more operations includes: If an ongoing UE-initiated 5G mobility management 5GMM procedure exists, terminate the ongoing UE-initiated 5G mobility management 5GMM procedure, and If a NAS signal connection exists, the NAS signal connection is released locally.
2. The method of claim 1, wherein the first event comprises: determining that the CAG ID becomes unauthorized based on the allowed CAG list; Determining that the CAG IDs supported by the current CAG cell are not authorized by the current PLMN in the CAG information list based on the allowed CAG list; as well as Determine whether the entry includes an indication indicating that the UE is only allowed to access the fifth generation system 5GS through the CAG cell.
3. The method of claim 2, wherein the first event comprises: Determine that the entry does not include the indication indicating that the UE is only allowed to access the 5GS through the CAG cell.
4. The method of claim 2, wherein the first event comprises: Determine that the entry includes the indication, which indicates that the UE is only allowed to access the 5GS through the CAG cell, and one or more CAG IDs are authorized in the CAG information list for the current PLMN based on the allowed CAG list.
5. The method of claim 2, wherein the first event comprises: determining that the entry includes the indication that the UE is only allowed to access the 5GS through a CAG cell, and no CAG ID is authorized in the CAG information list for the current PLMN based on the allowed CAG list; as well as It is determined that the UE has no emergency packet data unit (PDU) session.
6. The method of claim 1, further comprising: In response to a second event, if the ongoing UE-initiated 5GMM procedure exists, terminating the ongoing UE-initiated 5GMM procedure, The second event includes: determining that the CAG ID becomes unauthorized based on the allowed CAG list; Determining that the CAG IDs supported by the current CAG cell are not authorized by the current PLMN in the CAG information list based on the allowed CAG list; determining that the entry includes an indication that the UE is only allowed to access the fifth generation system 5GS through a CAG cell, and no CAG ID is authorized in the CAG information list for the current PLMN based on the allowed CAG list; and Determine that the UE has an emergency PDU session.
7. The method as claimed in claim 1, wherein the CAG ID is configured with time validity information in the allowed CAG list and indicates a time period, and when the current time of the UE matches the time period, the CAG ID is determined to be authorized, and when the current time of the UE does not match the time period, it is determined to be unauthorized based on the allowed CAG list.
8. A device for wireless communication, the device being a user equipment UE, comprising:
1. Memory; as well as At least one processor is connected to the memory and configured to: Maintaining a closed access group CAG information list including an entry, wherein the UE supports enhanced CAG information, the entry includes an allowed CAG list associated with a current public land mobile network PLMN, and the allowed CAG list includes one or more CAG identifiers ID; accessing the current PLMN via a current CAG cell having a CAG ID, wherein the CAG ID is determined to be authorized based on the allowed CAG list associated with the current PLMN; as well as In response to a first event, one or more operations are performed, including: If a UE-initiated 5G mobility management 5GMM procedure is in progress, the UE-initiated 5G mobility management 5GMM procedure is terminated. If a NAS signal connection exists, the NAS signal connection is released locally.
9. A non-transitory computer-readable medium storing computer-executable code for wireless communication of a user equipment UE, comprising: Maintaining a closed access group CAG information list including an entry, wherein the UE supports enhanced CAG information, the entry including an allowed CAG list associated with a current public land mobile network PLMN, and the allowed CAG list includes one or more CAG identifiers ID; accessing the current PLMN through a current CAG cell having a CAG ID, wherein the CAG ID is determined to be authorized based on the allowed CAG list associated with the current PLMN; and In response to a first event, one or more actions are performed, including: If there is an ongoing UE-initiated 5G mobility management 5GMM procedure, terminate the ongoing UE-initiated 5GMM procedure, and If there is a non-access layer NAS signaling connection, the NAS signaling connection is released locally.
