Method of handling emergency services for localizing changes between satisfaction and dissatisfaction of services
By dynamically adjusting network selection while meeting or not meeting the CAG validity conditions, the problem of unstable service quality in 5G NR technology is solved, and higher user experience and network switching efficiency are achieved.
Patent Information
- Application Number
- CN202410724714.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-06-04
- Filing Date
- 2024-06-05
- Publication Date
- 2024-12-06
AI Technical Summary
When 5G NR technology meets and does not meet the changes in CAG effectiveness, it is difficult to effectively manage the selection and handover between mobile stations and independent non-public networks, resulting in unstable service quality and user experience.
When the mobile station detects an emergency service or service effectiveness change, it executes the SNPN selection procedure to ensure that the network is switched when the conditions are met or not met, releases or establishes an emergency PDU session, and optimizes network selection to maintain service quality.
By dynamically adjusting network selection, the service stability and user experience of mobile stations while meeting or not meeting the CAG effectiveness conditions are improved, ensuring the reliability of emergency services and localized services.
Smart Images

Figure CN119095020A_ABST
Abstract
Description
Technical Field
[0001] The present application relates generally to communication systems, and more specifically to techniques for methods and devices for processing 5GMM procedures to cope with changes in CAG validity between satisfied and unsatisfied. 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 broadcasting. A typical wireless communication system may employ multiple access technologies capable of supporting communications 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 multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a municipal, national, regional, and even global level. An example is 5G New Radio NR. 5G NR is part of the ongoing mobile broadband evolution promoted by the 3rd Generation Partnership Project 3GPP and is designed 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. 5G NR technology requires further improvements. These improvements may also apply to other multi-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 a device are provided. The method can be performed by a mobile station MS. In certain configurations, the MS supports access to a selected independent non-public network SNPN that provides localized services and is in an automatic SNPN selection mode. The MS determines whether the MS has ongoing emergency services. In response to determining that the MS has no ongoing emergency services, the MS performs an SNPN selection procedure when a first event is triggered. In response to determining that the MS has ongoing emergency services, the MS determines whether the validity information of the selected SNPN is no longer satisfied. In response to determining that the validity information of the selected SNPN is no longer satisfied, the MS performs a local release of all emergency PDU sessions except emergency PDU sessions. After the emergency PDU session is released, the MS performs the SNPN selection procedure when the first event is triggered.
[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 of a wireless communication system and access network.
[0009] Figure 2 is an example diagram of 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 a diagram showing an example of a downlink (DL)-centric time slot.
[0013] Figure 6 is a diagram showing an example of an uplink (UL)-centric time slot.
[0014] Figure 7 is a diagram showing a communication system with a public land mobile network (PLMN), a standalone non-public network (SNPN), and a PNO-NPN / CAG providing localized service access.
[0015] Figure 8 is a flow chart of an example procedure for a mobile station (MS).
[0016] Fig. 9 is a diagram illustrating an example procedure of a mobile station (MS) responding to a first event.
[0017] Fig.10 is a diagram illustrating an example procedure of a mobile station (MS) responding to a first event.
[0018] Fig.11 is a diagram illustrating an example procedure of a mobile station (MS) responding to a first event.
[0019] Fig.12 is a diagram illustrating an example procedure of a mobile station (MS) responding to a first event.
[0020] Fig.13 is a flow chart of an example procedure for a mobile station (MS).
[0021] Fig.14 is a flow chart of an example procedure for a mobile station (MS).
[0022] Fig.15 The present invention is a flow chart of a mobile station (MS) wireless communication method (process). DETAILED DESCRIPTION
[0023] 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.
[0024] Several aspects of telecommunication systems will now be described with reference to various devices and methods. These devices 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.
[0025] For example, an element, any part 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.
[0026] 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 that can be accessed by a computer, whether in the form of instructions or data structures.
[0027] 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 base stations (high-power cellular base stations) and / or small base stations (low-power cellular base stations). Macro base stations include base stations. Small base stations include home base stations, micro base stations, and pico base stations.
[0028] 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. The 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.
[0029] Base stations 102 may communicate wirelessly with user equipment 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 base station 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 base stations and macro base stations 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). A communication link 120 between a base station 102 and a user equipment 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the user equipment 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the user equipment 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. Base station 102 / user equipment 104 can use spectrum with bandwidth of up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz), with carrier aggregation totaling Yx MHz (x component carriers) for transmission in each direction per carrier. Carriers may or may not be adjacent. Allocated carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL). 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).
[0030] Some user devices 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 side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication may be performed through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.
[0031] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with Wi-Fi stations (STAs) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.
[0032] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' can adopt New Radio (NR) and use the same 5 GHz unlicensed spectrum as the Wi-Fi AP 150. The small cell 102' adopts NR in the unlicensed spectrum to enhance the coverage and / or increase the capacity of the access network.
[0033] The base station 102, whether a small cell 102' or a large cell (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 operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near millimeter wave frequencies for communicating with UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. Extremely high frequency (EHF) is part of the radio frequency (RF) in the electromagnetic spectrum. The EHF range is 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. Near millimeter waves may extend to frequencies of 3 GHz with wavelengths of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Using the millimeter wave / near millimeter wave radio frequency bands (e.g., 3 GHz-300 GHz) for communication has extremely high path loss and short distances. The mmWave base station 180 may communicate with the UE 104 using beamforming 182 to compensate for the extremely high path loss and short range.
[0034] The base station 180 may send beamformed signals in one or more transmit directions 108a to the UE 104. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 108b. The UE 104 may also send beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for 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.
[0035] 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 signaling 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 the functionality for MBMS user service configuration and delivery. 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 broadcast multicast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.
[0036] 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 signaling 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 transported 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, the intranet, the IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.
[0037] 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 receive point (TRP), or other suitable terminology. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, a utility meter, a gas pump, a large or small kitchen appliance, a medical device, an implant, a sensor / actuator, a display, or any other device with similar functionality. 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 station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, 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 suitable terminology.
[0038] Although the present disclosure may refer to 5G New Radio (NR), the present disclosure may also be applicable 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 wireless / wireless access technologies.
[0039] 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 Packet Core (EPC) 160 may 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, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 275 provides RRC layer functions related to system information (e.g., MIB, SIBs) broadcast, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), cross-radio access technology (Radio Access Technology, referred to as RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to upper layer packet data unit (Packet data Units, referred to as PDUs) transmission, error correction through automatic repeat request (Automatic Repeat reQuest, referred to as ARQ), RLC service data unit (Service data Units, referred to as SDUs) connection, segmentation and reassembly, RLC data PDUs re-segmentation, and RLC data PDUs reordering; and mapping between logical channels and transport channels, MAC SDUs to transport blocks (Transport The MAC layer functions include multiplexing of MAC SDUs (Blocks, TBs for short), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through Hybrid Automatic RepeatreQuest (HARQ), priority processing and logical channel priority-related MAC layer functions.
[0040] The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functions associated with various signal processing functions. Layer 1 includes the physical (PHY) layer, which may include error detection of the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and multiple input multiple output (MIMO) antenna processing. The TX processor 216 processes signal constellation mapping 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 divided into parallel streams. Each stream may then be mapped to an Orthogonal Frequency Division Multiplexing (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 the channel estimator 274 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals 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 a radio frequency (RF) carrier with a corresponding spatial stream for transmission.
[0041] 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 directed to the UE 250. If multiple spatial streams are directed to the UE 250, they may be combined into one 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 OFDM signal subcarrier. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 210. 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 base station 210. The data and control signals are then provided to controller / processor 259 which implements Layer 3 and Layer 2 functions.
[0042] 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 acknowledgement (ACK) and / or negative acknowledgement (NACK) protocol to support HARQ operations.
[0043] Similar to the downlink transmission functions of the base station 210, the 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 upper layer PDUs transmission, error correction through ARQ, connection, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing and logical channel priority.
[0044] 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 uplink transmission is processed at the base station 210 in a manner similar to the UE 250 receive function. Each receiver 218RX receives the signal through its corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 270.
[0045] 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 ACK and / or NACK protocol to support HARQ operations.
[0046] 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 utilize orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on 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 MTC technologies, and / or mission critical services for ultra-reliable low latency communication (URLLC) services.
[0047] 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 of data transmission (i.e., downlink (DL) or uplink (UL)), 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. NR's UL and DL time slots may be as follows: Figure 5 and Figure 6 Describe in more detail.
[0048] 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 UEs 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 for cell selection, access, handover, and / or measurement based on the indicated cell type.
[0049] Figure 3 An example logical architecture of a distributed RAN 300 is shown, in accordance with aspects of the present disclosure. 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 described above, TRP may be used interchangeably with "cell".
[0050] TRPs 308 may be a distribution 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, a TRP may be connected to multiple ANCs. A TRP may include one or more antenna ports. TRPs may be configured to serve traffic for UEs individually (e.g., dynamically selected) or collectively (e.g., joint transmission).
[0051] The local architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. The architecture can define fronthaul solutions that support different deployment types. For example, the architecture can be based on transport network capabilities (e.g., bandwidth, latency and / or jitter). The architecture can share features and / or components with LTE. According to aspects, the next generation AN (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.
[0052] The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be provisioned within a TRP and / or across TRPs by ANC 302. Depending on aspects, an inter-TRP interface may not be required / present.
[0053] According to aspects, there may be dynamic configuration of split logic functions in the architecture of the distributed RAN 300. PDCP, RLC, MAC protocols may be adaptively placed at the ANC or TRP.
[0054] Figure 4 An example physical architecture of a distributed RAN 400 is shown, in accordance with aspects of the present disclosure. A centralized core network unit (C-CU) 402 can host core network functions. The C-CU can be centrally deployed. C-CU functions can be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity. A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can have a distributed deployment. The C-RU can be closer to the edge of the network. A distributed unit (DU) 406 can host one or more TRPs. The DU can be located at the edge of the network with radio frequency (RF) functions.
[0055] Figure 5Example 500 is labeled, showing an example of a downlink (DL)-centric time slot. The downlink-centric time slot may include a control portion 502. The control portion 502 may be present at an initial or beginning portion of the downlink-centric time slot. The control portion 502 may include various scheduling information and / or control information corresponding to various portions of the downlink-centric time slot. 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 user equipment or a base station) to a subordinate entity (e.g., a user equipment). In some configurations, the downlink data portion 504 may be a physical downlink shared channel (PDSCH).
[0056] The downlink-centric time slot may also include a common uplink 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 other 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 acknowledgment signal (ACK), a negative acknowledgement signal (NACK), 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.
[0057] 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., user equipment)) to uplink communications (e.g., transmissions by a subordinate entity (e.g., user equipment)). It will be appreciated by those of ordinary skill in the art 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.
[0058] Figure 6An example of an uplink (UL) centric timeslot is shown labeled 600. 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., user equipment) to the scheduling entity (e.g., user equipment or base station). In some configurations, the control portion 602 may be a physical downlink control channel (PDCCH).
[0059] like Figure 6 As 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.
[0060] In some cases, two or more slave entities (e.g., user devices) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, user device 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 from one slave entity (e.g., UE1) to another slave entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., user device or base station), although 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).
[0061] 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 bands. Access to PLMN services is achieved through an air interface involving radio communications between mobile phones and base stations, in which IP network services are integrated. A PLMN may include multiple radio access networks (RANs) using different radio access technologies (RATs) to access mobile services. The radio access network is part of a mobile communication system that implements radio access technologies. Conceptually, the RAN is located between mobile devices and their core network (CN) to provide connectivity. According to the standards, mobile phones and other wireless connected devices are called 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.
[0062] In contrast to a PLMN, a non-public network (NPN) is a network used for non-public purposes. An NPN can be a standalone non-public network (SNPN), i.e. operated by an NPN operator and not dependent on the network functionality provided by a PLMN, or a public network integrated NPN (PNI-NPN), i.e. a non-public network deployed with the support of a PLMN. A credential holder (CH) can authenticate and authorize access to a SNPN, separate from the credential holder. The combination of a PLMN ID and a network identifier (NID) identifies a SNPN. User equipment may be enabled for use with a SNPN.
[0063] A PNI-NPN is an NPN provided over a PLMN, such as through 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 network slice assigned to the NPN is not allowed, 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. CAGs are used for PNI-NPNs to prevent UEs that are not allowed to access the NPN through the associated cell from automatically selecting and accessing the associated CAG cell. CAGs are used for access control, such as authorization at the time of cell selection, and are configured in a subscription as part of mobility restrictions. A CAG is identified by a CAG identifier, which is unique within the PLMN ID range.
[0064] Local or localized services are services that are provided in a specific / limited area or are time-limited. Localized service providers are application providers or network operators who localize their services and provide them to end-users through a hosted network. A hosted network is a network that provides localized services and can be a SNPN or PNI-NPN, while a home network is a network that has a subscription or credentials currently used by the UE. A 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 localized services.
[0065] In order to provide the UE with access to localized services, the UE needs to be able to discover, select and access an NPN (as a hosting network) that provides localized services.
[0066] Figure 7 FIG. 7 is a diagram of a communication system 700 including a PLMN 710, a SNPN 720 and a public network integrated NPN (PNI-NPN) / CAG 730, providing access to localized services. 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. RAN 740 provides radio access to UE 701 via RAT. An access and mobility management function (AMF) in PLMN 710 communicates with gNB 712. UE 701 may be equipped with one or more radio frequency (RF) transceivers.
[0067] 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. The combination of PLMN ID and network identifier (NID) identifies a SNPN. The serving base station (e.g., gNB) 722 is part of the radio access network (RAN) 750. RAN 750 provides radio access to UE 701 via RAT. The AMF in the SNPN 720 communicates with the gNB 722. The SNPN 720 is operated by the NPN operator and does not rely on network functions provided by the public network. The credential holder (CH) can authenticate and authorize access to the SNPN individually. 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 of non-public networks to which each PLMN ID identifies the NG-RAN provides access. A UE supporting SNPN is configured with a PLMN ID and NID (SNPN ID) for subscribing to SNPN, and a SNPN-enabled UE supporting access to SNPN using credentials from a credential holder may also be configured with registration information 702 for SNPN selection (SNPN selection information or configuration) and using SNPN subscription or using PLMN subscription (USIM) (in SNPN access mode).
[0068] 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. CAG is used for 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, which is unique within the PLMN ID range. 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.
[0069] Localized services are services provided in a specific / limited area or are time-limited services (specific time period). Localized services are providers of commercial applications or network operators who localize their services and provide them to end users through a hosted network. The hosted network is the network that provides 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 , both SNPN 720 and PNI-NPN (CAG) 730 may be hosted networks that provide localized service access to UE 701.
[0070] When the localized service in a network is completed, all user equipment (UE) registered with the network are expected to 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 may stop using network resources to obtain 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 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 as part of the localized service information to restrict the user equipment from accessing the SNPN / PNI-NPN (as a hosting network) that provides localized services. In order to provide localized services to user equipment, the user equipment needs to be able to discover, select and access the SNPN / PNI-NPN (as a hosting network) that provides localized services. The discovery mechanism is based on providing or configuring appropriate information to the user equipment.
[0071] Figure 8 800 is a flow chart of an example procedure for a mobile station (MS). The example procedure 800 may be performed by a mobile station (eg, user equipment 701). Figure 8As shown, in procedure 810, the mobile station supports access to the selected SNPN to provide localized services in the selected SNPN, and the mobile station is in automatic SNPN selection mode. In procedure 820, the mobile station determines whether the mobile station has ongoing emergency services. In some embodiments, the mobile station determines that the mobile station has ongoing emergency services when at least one condition is met. These conditions include: the mobile station has an emergency packet data unit (PDU) session for emergency services, and the mobile station has registered for emergency services. In other words, the mobile station determines that the mobile station has ongoing emergency services when the mobile station has an emergency PDU session for emergency services, or the mobile station has registered for emergency services, or both. On the other hand, when the mobile station has no emergency PDU session, no emergency PDU session is established, no emergency services are registered, no emergency services are registered, and high priority access is not configured in the selected SNPN, the mobile station determines that there are no ongoing emergency services. After determining that the mobile station has no ongoing emergency services, in procedure 830, the mobile station determines whether a first event is triggered. When the first event is triggered, in procedure 840, the mobile station performs an SNPN selection procedure.
[0072] In some configurations, the first event may involve conditions that the mobile station has no emergency PDU session, the mobile station is not registered for emergency services, and the state of localized service access in the selected SNPN. Examples of the first event are described in detail below.
[0073] Fig. 9 is a diagram of an example procedure showing the mobile station responding to the first event. Fig. 9 As shown, in the example procedure 900, the mobile station 902 (e.g., the user equipment 701) has no emergency PDU session and has not registered for emergency services. In procedure 910, the mobile station 902 determines that there is no ongoing emergency service. In procedure 930, the mobile station 902 determines that when a first event occurs, the access to the localized service in the selected SNPN changes, that is, the access to the localized service in the selected SNPN changes between disabled and enabled. In response to the first event 930, in procedure 950, the mobile station 902 performs the SNPN selection procedure.
[0074] Fig.10 is a diagram of an example procedure showing the mobile station responding to the first event. Fig.10As shown, in example procedure 1000, mobile station 1002 (e.g., user equipment 701) has no emergency PDU session and has not registered for emergency services. In procedure 1010, mobile station 1002 determines that there are no ongoing emergency services. In procedure 1020, mobile station 1002 determines that localized service access in the selected SNPN is enabled, and the selected SNPN is selected according to clause 4.9.3.1.1 a0) specified in 3GPP TS23.122 (i.e., the selected SNPN provides localized services to mobile station 1002). In procedure 1030, mobile station 1002 determines that a first event occurs when the validity information of the selected SNPN is no longer satisfied. In response to the first event 1030, in procedure 1050, mobile station 1002 performs an SNPN selection procedure.
[0075] Fig.11 is a diagram of an example procedure showing the mobile station responding to the first event. Fig.11 As shown, in the example procedure 1100, the mobile station 1102 (e.g., the user equipment 701) has no emergency PDU session and has not registered for emergency services. In procedure 1110, the mobile station 1102 determines that there is no ongoing emergency service. In procedure 1120, the mobile station 1102 determines that localized service access in the selected SNPN is enabled, and the selected SNPN is not selected according to clause 4.9.3.1.1 a0) specified in 3GPP TS23.122 (i.e., the selected SNPN does not provide localized services to the mobile station 1102). In procedure 1130, the mobile station 1102 determines that a first event occurs when validity information (e.g., time validity information) of one or more SNPNs is identified by one or more SNPN identifiers and is contained in an entry of the "preferred SNPN list controlled by the voucher holder for priority access to localized services in the SNPN". In response to the first event 1130, in procedure 1150, the mobile station 1102 performs an SNPN selection procedure.
[0076] Fig.12 is a schematic diagram showing an example procedure of the MS in response to the first event. Fig.12As shown, in example procedure 1200, MS1202 (e.g., UE 701) has no emergency PDU session and is not registered for emergency services. In procedure 1210, MS1202 determines that there are no ongoing emergency services. In procedure 1220, MS1202 determines that access to localized services is enabled in the selected SNPN, and the selected SNPN is not selected in accordance with clause a0 of 4.9.3.1.1 specified in 3GPP TS23.122 (i.e., the selected SNPN does not provide localized services to MS1202). In procedure 1230, MS1202 determines that a first event has occurred when the validity information (e.g., time validity information) of one or more GINs identified in an entry in the "preferred GINs list controlled by the credential holder for priority access to localized services in the SNPN" is satisfied. In response to the first event 1230, in procedure 1250, MS1202 performs an SNPN selection procedure.
[0077] To summarize example procedures 900, 1000, 1100, and 1200, the first event may include: the MS does not have an emergency PDU session, has not established an emergency PDU session, is not registered for emergency services, is not registered for emergency services, and is not configured for high priority access in the selected SNPN, and (1) access to localized services in the SNPN is switched between disabled and enabled, or (2) localized service access is enabled in the SNPN, the selected SNPN is selected in accordance with clause a0 of 4.9.3.1.1 specified in 3GPP TS23.122 (i.e., the selected SNPN provides localized services to the MS), and the validity information of the selected SNPN is no longer satisfied, or (3) localized service access is enabled in the SNPN, the selected SNPN is selected in accordance with clause a0 of 3GPP TS23.122. The time validity information of one or more SNPNs identified in the "list of preferred SNPNs controlled by the voucher holder for priority access to localized services in the SNPN" or the time validity information of one or more GINs identified in the "list of preferred GINs controlled by the voucher holder for priority access to localized services in the SNPN" as specified in TS23.122 is satisfied.
[0078] Fig.13 is a flow chart of an example procedure of an MS. The example procedure 1300 may be performed by an MS (eg, UE 701). Figure 8, in procedure 820, it is determined whether the MS has ongoing emergency services, and it is determined that the MS has no ongoing emergency services. In certain configurations, in response to determining that the MS has ongoing emergency services (e.g., when the MS has an emergency PDU session for emergency services, or the MS has registered for emergency services, or both), in procedure 1310, the MS monitors whether the emergency PDU session is released or whether the MS no longer has ongoing emergency services. In response to determining that the emergency PDU session is released or the MS no longer has ongoing emergency services, in procedure 1320, the MS performs an SNPN selection procedure. In other words, the MS performs the SNPN selection procedure after the emergency PDU session is released or the MS no longer has ongoing emergency services.
[0079] Fig.14 is a flow chart of an example procedure of an MS. The example procedure 1400 may be performed by an MS (eg, UE 701). Figure 8 , in procedure 820, the MS determines whether there is an ongoing emergency service, and has determined that the MS has no ongoing emergency service. In some configurations, in response to determining that the MS has an ongoing emergency service (for example, when the MS has an emergency PDU session for emergency services, or the MS has registered for emergency services, or both), in procedure 1410, the MS determines whether the validity information of the selected SNPN is no longer satisfied. In response to determining that the validity information of the selected SNPN is no longer satisfied, in procedure 1420, the MS performs a local release of all PDU sessions except the emergency PDU session. In this case, in procedure 1430, the MS determines whether a second event has occurred. In some embodiments, the second event includes: the PDU establishment procedure for the emergency PDU session and / or high priority access is completed, the emergency PDU session and / or the PDU session for high priority access is released, the registration procedure for the emergency service and / or high priority access is completed, and the MS is no longer registered for emergency services and / or high priority access. When the second event occurs, in procedure 1440, the MS performs an SNPN selection procedure. In other words, the MS does not perform the SNPN selection procedure until the second event occurs (i.e., the PDU establishment procedure for the emergency PDU session and / or high priority access is completed, the emergency PDU session and / or the PDU session for high priority access is released, the registration procedure for the emergency service and / or high priority access is completed, or the MS is no longer registered for emergency service and / or high priority access).
[0080] Fig.1515 is a flowchart of a method (process) for MS wireless communication. The method can be performed by an MS (e.g., UE710). In certain configurations, the MS supports access to a selected SNPN that provides localized services and is in an automatic SNPN selection mode. In operation 1510, the MS determines whether there is an ongoing emergency service. In response to determining that the MS has no ongoing emergency service, in operation 1520, the MS performs an SNPN selection procedure when a first event is triggered. In operation 1530, in response to determining that the MS has an ongoing emergency service, the MS determines whether the validity information of the selected SNPN is no longer satisfied. In operation 1540, in response to determining that the validity information of the selected SNPN is no longer satisfied, the MS performs a local release of all emergency PDU sessions except the emergency PDU session. In operation 1550, the MS performs an SNPN selection procedure when the first event is triggered after the emergency PDU session is released.
[0081] In some configurations, the MS determines that the MS has an ongoing emergency service when at least one condition is met, including that the MS has an emergency PDU session for the emergency service and the MS has registered for the emergency service.
[0082] In certain configurations, the MS does not perform the SNPN selection procedure until: the PDU establishment procedure for the emergency PDU session and / or high priority access is completed, the emergency PDU session and / or the PDU session for high priority access is released, the registration procedure for the emergency service and / or high priority access is completed, and the MS is no longer registered for emergency service and / or high priority access.
[0083] In some configurations, the first event includes switching between enabling and disabling access to localized services for the MS in the selected SNPN.
[0084] In certain configurations, the first event includes enabling access to localized services in the selected SNPN, the selected SNPN being selected according to item a0) of Section 4.9.3.1.1 of 3GPP TS23.122 (i.e., the selected SNPN provides localized services to the MS in the SNPN), and the validity information of the selected SNPN is no longer satisfied.
[0085] In certain configurations, the first event includes enabling access to localized services in the selected SNPN, which is not selected according to item a0) of Section 4.9.3.1.1 of 3GPP TS23.122, and identifying validity information of one or more SNPNs of an entry in the "preferred SNPN list for priority access to localized services in SNPNs controlled by the credential holder".
[0086] In certain configurations, the first event includes enabling access to localized services in the selected SNPN, which is not selected according to clause 4.9.3.1.1 a0) of 3GPP TS23.122, and identifying validity information of one or more GINs of an entry in a "list of preferred GINs controlled by the credential holder for priority access to localized services in the SNPN".
[0087] 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.
[0088] 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 mobile station MS, characterized in that: include: Determining whether the MS has an ongoing emergency service, wherein the MS supports access to a selected independent non-public network (SNPN), the selected SNPN providing localized service access in the SNPN, and the MS is in an automatic SNPN selection mode; In response to determining that the MS has no ongoing emergency service, performing an SNPN selection procedure when a first event is triggered; and In response to determining that the MS has an ongoing emergency service, performing operations including the following: Determining whether the validity information of the selected SNPN is no longer satisfied; In response to determining that the validity information of the selected SNPN is no longer satisfied, performing a local release of all emergency data packet unit (PDU) sessions except an emergency data packet unit (PDU) session; and After the emergency PDU session is released, the SNPN selection procedure is performed when the first event is triggered.
2. The method according to claim 1, characterized in that Further including: Determining that the MS has an ongoing emergency service when at least one condition is met, wherein the condition comprises: The MS has the emergency PDU session for emergency services, and The MS is registered for emergency services.
3. The method according to claim 1, characterized in that The MS does not perform the SNPN selection procedure before the following circumstances: The PDU establishment procedure and / or high priority access for this emergency PDU session is completed, The emergency PDU session and / or the high priority access PDU session are released, Completion of the registration process for emergency services and / or high priority access, and The MS is no longer registered for emergency services and / or high priority access.
4. The method according to claim 1, characterized in that The first event includes: Switching between enabling and disabling access of localized services for the MS in the selected SNPN.
5. The method according to claim 1, characterized in that The first event includes: Localized service access in the selected SNPN is enabled, and The selected SNPN provides localized services to the MS in the SNPN, and The validity information of the selected SNPN is no longer satisfied.
6. The method according to claim 1, characterized in that The first event includes: Localized service access in the selected SNPN is enabled, and The validity information of one or more SNPNs identifying an entry in the "preferred SNPN list controlled by the credential holder for priority access to localized services in the SNPN" changes from not satisfied to satisfied.
7. The method according to claim 1, characterized in that The first event includes: Localized service access in the selected SNPN is enabled, and The validity information of one or more GINs identifying an entry in the "Credential Holder Controlled List of Preferred GINs for Priority Access to Localized Services in the SNPN" changes from Not Satisfied to Satisfied.
8. A device for wireless communication, the device being a mobile station MS, characterized in that: include: a memory; as well as At least one processor is coupled to the memory and configured to: Determining whether the MS has an ongoing emergency service, wherein the MS supports access to a selected independent non-public network (SNPN), the selected SNPN provides localized service access, and the MS is in an automatic SNPN selection mode; In response to determining that the MS has no ongoing emergency service, performing an SNPN selection procedure when a first event is triggered; and In response to determining that the MS has an ongoing emergency service, performing operations including the following: Determining whether the validity information of the selected SNPN is no longer satisfied; In response to determining that the validity information of the selected SNPN is no longer satisfied, performing a local release of all emergency PDU sessions except one emergency PDU session; and After the emergency PDU session is released, the SNPN selection procedure is performed when the first event is triggered.
9. A non-transitory computer readable medium storing computer executable code for wireless communication of a mobile station MS, characterized in that: Include code to: determining whether the MS has an ongoing emergency service, wherein the MS supports access to a selected independent non-public network (SNPN) providing localized services, and the MS is in an automatic SNPN selection mode; In response to determining that the MS does not have the ongoing emergency service, performing an SNPN selection procedure when a first event is triggered; as well as In response to determining that the MS has the ongoing emergency service, performing operations including the following: determining whether validity information for the selected SNPN is no longer satisfied; In response to determining that the validity information of the selected SNPN is no longer satisfied, performing a local release of all emergency packet data unit (PDU) sessions except an emergency PDU session; and After the first event is triggered, the SNPN selection procedure is performed after the emergency PDU session is released.
