Method and apparatus for handling operations in standalone non-public network (SNPN)

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure is for handling operations in a standalone non-public network (SNPN). Embodiments herein disclose a method for handling operation in a standalone non-public network (SNPN) by a UE. The method includes determining that the dialed number is an emergency number. Further, the method includes determining that the current SNPN does not support the emergency service of the dialed number. Further, the method includes performing a logout procedure upon determining that the current SNPN does not support the emergency service of the dialed number. Further, the method includes selecting at least one of a cell and a public land mobile network (PLMN) that provide the emergency service to the UE after performing the logout procedure.

Description

Technical Field

[0001] The embodiments disclosed herein relate to wireless networks, and more particularly, to handling emergency calls when network access is performed in a Standalone Non-Public Network (SNPN), and more particularly, to a system and method for handling the last registered Standalone Non-Public Network (SNPN). Background Art

[0002] The 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services, which can be achieved not only in the "sub-6 GHz" band such as 3.5 GHz, but also in the "above-6 GHz" band called mmWave including 28 GHz and 39 GHz. In addition, the 6G mobile communication technology (referred to as the Ultra 5G system) has been considered in the terahertz band (e.g., 95 GHz to 3 THz band) in order to achieve a transmission rate fifty times faster than that of the 5G mobile communication technology and an ultra-low latency of one-tenth of that of the 5G mobile communication technology.

[0003] At the beginning of the development of the 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC), there has been continuous standardization on beamforming and massive MIMO for reducing radio wave path loss and increasing the radio wave transmission distance in mmWave, supporting parameter sets for dynamic operations for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technologies for supporting multi-beam transmission and broadband, the definition and operation of BWP (bandwidth part). New channel coding methods such as LDPC (Low-Density Parity-Check) codes for large data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by the 5G mobile communication technology, there has been continuous discussion on the improvement and performance enhancement of the initial 5G mobile communication technology, and there has been physical layer standardization on technologies such as V2X (Vehicle-to-Everything) for assisting the driving determination of autonomous vehicles based on information about the position and status of vehicles sent by vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation compliant with various regulatory requirements in the unlicensed band, NR UE power saving, non-terrestrial network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with the terrestrial network is unavailable, and positioning.

[0005] In addition, there is continuous standardization of air interface architectures / protocols for technologies such as industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, integrated access and backhaul (IAB) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and dual active protocol stack (DAPS) handover, and two-step random access (two-step RACH for NR) for simplifying the random access process. There is also continuous standardization of system architectures / services for 5G baseline architectures (e.g., service-based architecture or service-based interface), for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, and for mobile edge computing (MEC) for receiving services based on UE location.

[0006] As the 5G mobile communication system is commercialized, the exponentially growing connected devices will be connected to the communication network, and accordingly, enhanced functions and performance of the 5G mobile communication system and integrated operation of the connected devices are expected to be necessary. For this purpose, new research related to extended reality (XR) is arranged to effectively support augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., and to improve 5G performance and reduce complexity by leveraging artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] In addition, the development of such 5G mobile communication systems will serve as the basis for not only developing new waveforms for providing terahertz band coverage for 6G mobile communication technologies, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and high-dimensional spatial multiplexing technologies of reconfigurable intelligent surfaces (RIS), but also developing full-duplex technologies for improving the frequency efficiency of 6G mobile communication technologies and enhancing the system network, AI-based communication technologies for realizing system optimization and internalizing end-to-end AI support functions by leveraging satellites and AI (artificial intelligence) from the design stage, and next-generation distributed computing technologies for realizing services beyond complex levels. UEs can limit the limitations of UE operation capabilities by leveraging ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical Problem

[0009] The main objective of the embodiments herein is to handle operations in a standalone non-public network (SNPN).

[0010] Another object of embodiments of the present disclosure is to handle emergency calls when a UE (SNPN enabled) is networked in an SNPN.

[0011] Another object of embodiments of the present disclosure is to handle the last registered SNPN.

[0012] Another object of embodiments of the present disclosure is to preferentially select a subscribed SNPN rather than a registered SNPN during an activation process or during operation in an SNPN access mode process.

[0013] The present disclosure has been made to solve at least the above problems and / or disadvantages and to provide at least the advantages described below. Accordingly, one aspect of the present disclosure provides a method and apparatus for handling operations in a Standalone Non-Public Network (SNPN).

[0014] Solution to the problem

[0015] Accordingly, embodiments herein provide a method for handling operations in an SNPN. The method includes the UE determining that the dialed number is an emergency number. In addition, the method includes the UE determining that the current SNPN does not support emergency services for the dialed number. In addition, the method includes the UE performing a deregistration process when determining that the current SNPN does not support emergency services for the dialed number. In addition, the method includes the UE, after performing the deregistration process, selecting at least one of a cell and a Public Land Mobile Network (PLMN) that provides emergency services to the UE.

[0016] In an embodiment, the method includes the UE placing an emergency service call over the PS domain when selecting at least one of a cell and a PLMN.

[0017] In an embodiment, the method includes the UE, when selecting at least one of a cell and a PLMN, establishing a Protocol Data Unit (PDU) session for the emergency service. In addition, the method includes the UE continuing the emergency service in at least one of the cell and the PLMN.

[0018] In an embodiment, the UE determines that the dialed number is an emergency number when one of the following occurs: the UE is registered for access service in the SNPN, and the UE is registering for access service in the SNPN.

[0019] In an embodiment, the emergency service includes an emergency call and an emergency message.

[0020] In an embodiment, the deregistration process is one of a local deregistration or a deregistration with the network.

[0021] Accordingly, embodiments of the present disclosure provide a method for handling operations in an SNPN. The method includes a UE determining that the UE is in an automatic selection mode. Additionally, the method includes the UE determining the coverage of a subscribed SNPN when it is determined that the UE is in the automatic selection mode. Additionally, the method includes the UE selecting and registering the subscribed SNPN based on this determination.

[0022] In an embodiment, the method includes, after determining that the coverage of the subscribed SNPN is available, the UE stopping to return one of a registered SNPN and an equivalent SNPN.

[0023] In an embodiment, the UE is in the automatic selection mode when the UE is powered on or the UE starts operating in the SNPN access mode or follows a recovery from a lack of coverage, or when the UE changes an entry in the subscriber data list.

[0024] In an embodiment, selecting the subscribed SNPN indicates that the UE selects and registers the subscribed SNPN of the selected entry in the subscriber data list.

[0025] Accordingly, embodiments of the present disclosure provide a UE including an SNPN-based controller coupled to a processor and a memory. The SNPN-based controller is configured to determine that a dialed number is an emergency number. Additionally, the SNPN-based controller is configured to determine that the current SNPN does not support emergency services for the dialed number. Additionally, the SNPN-based controller is configured to perform a deregistration process when it is determined that the current SNPN does not support emergency services for the dialed number. Additionally, the SNPN-based controller is configured to select at least one of a cell and a PLMN that provides emergency services to the UE after performing the deregistration process.

[0026] Accordingly, embodiments of the present disclosure provide a UE including an SNPN-based controller coupled to a processor and a memory. The SNPN-based controller is configured to determine that the UE is in an automatic selection mode. Additionally, the SNPN-based controller is configured to determine the coverage of the subscribed SNPN when it is determined that the UE is in the automatic selection mode. Additionally, the SNPN-based controller is configured to select and register the subscribed SNPN based on this determination.

[0027] These and other aspects of the embodiments of the present disclosure will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. However, it should be understood that the following description, although indicating at least one embodiment and many of its specific details, is given by way of illustration and not limitation. Many changes and modifications may be made within the scope of the embodiments of the present disclosure without departing from the spirit thereof, and the embodiments of the present disclosure include all such modifications.

[0028] Advantages of the Invention

[0029] A detailed description of exemplary embodiments of the present disclosure is disclosed in conjunction with the following drawings, and the advantages and significant features of the present disclosure will become apparent to those skilled in the art. For more enhanced communication systems, methods and apparatuses for handling operations in a Standalone Non-Public Network (SNPN) are needed. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Embodiments disclosed herein are illustrated in the drawings, and throughout the drawings, like reference numerals indicate corresponding parts in each of the drawings. The embodiments herein will be better understood from the following description with reference to the drawings, where:

[0031] Figure 1 An example flow of events in an existing method when processing the last registered SNPN according to an embodiment disclosed herein is shown;

[0032] Figure 2 An example flow of events depicting events in an existing method when processing the last registered SNPN according to an embodiment disclosed herein is shown;

[0033] Figure 3 An example scenario for enabling a UE to place an emergency call according to an embodiment disclosed herein is shown, where the UE currently cannot place an emergency call in an ON-SNPN;

[0034] Figure 4 An example scenario for enabling a UE to place an emergency call according to an embodiment disclosed herein is shown, where the UE currently cannot place an emergency call in an ON-SNPN;

[0035] Figure 5 An example scenario for enabling a UE to place an emergency call according to an embodiment disclosed herein is shown, where the UE currently cannot place an emergency call in an ON-SNPN because the SNPN does not support emergency services;

[0036] Figure 6 An example scenario according to an embodiment disclosed herein is shown, where the UE continues to place an emergency call in the same ON-SNPN that supports emergency services;

[0037] Figure 7 An example scenario according to an embodiment disclosed herein is shown, where the UE continues to place an emergency call in the same ON-SNPN that supports emergency services;

[0038] Figure 8 A flowchart showing an exemplary method for handling the last registered SNPN according to an embodiment disclosed herein is shown;

[0039] Figure 9A flowchart showing an exemplary call flow when processing the last registered SNPN according to an embodiment disclosed herein;

[0040] Figure 10 Shows various hardware components of a UE according to an embodiment disclosed herein;

[0041] Figure 11 A flowchart showing a method for processing operations in an SNPN while processing emergency services during network access in the SNPN according to an embodiment disclosed herein;

[0042] Figure 12 A flowchart showing a method for processing operations in an SNPN while processing the last registered SNPN according to an embodiment disclosed herein;

[0043] Figure 13 Shows a UE in a wireless communication system according to an embodiment disclosed herein;

[0044] Figure 14 Shows a base station in a wireless communication system according to an embodiment disclosed herein; and

[0045] Figure 15 Shows a network entity according to an embodiment disclosed herein. Detailed Description

[0046] Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: The terms "include" and "comprise," and derivatives thereof, mean including but not limited to; the term "or" is inclusive and means and / or; the phrases "associated with" and "associated therewith," and derivatives thereof, may mean including, being included within, interconnected with, containing, being contained within, connected to or coupled with, capable of communicating with, cooperating with, interlacing, juxtaposing, proximate to, bound to or bound with, having, having the property of, etc.; and the term "controller" means any device, system, or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware, software, or some combination of at least two thereof. It should be noted that the functions associated with any particular controller may be centralized or distributed, whether local or remote.

[0047] In addition, the various functions described below can be implemented or supported by one or more computer programs, each formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof that are adapted to be implemented in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.

[0048] Throughout this patent document, definitions of certain words and phrases are provided. Those of ordinary skill in the art should understand that, in many if not most instances, such definitions apply to the prior as well as future use of the words and phrases so defined.

[0049] The following specification particularly describes the present disclosure and the manner in which it is to be executed:

[0050] The following discussion Figures 1 to 15 and the various embodiments used to describe the principles of the present disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0051] Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "coupled" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms "send," "receive," and "communicate" and their derivatives cover both direct and indirect communication. The terms "comprise" and "include" and their derivatives mean including but not limited to. The term "or" is inclusive and means and / or. The phrase "associated with" and its derivatives mean including, being included within, connected to, interconnected with, containing, being contained within, connected to or coupled with, capable of communicating with, cooperating with, interlacing, juxtaposing, adjacent to, bound to or bound with, having, having the property of, having a relationship to or being related to, and the like. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or in a combination of hardware and software and / or firmware. The functions associated with any particular controller may be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items may be used and that possibly only one item from the list is required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B, and C. For example, "at least one of A, B, or C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B, and C.

[0052] In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed of computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof that are adapted to be implemented in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer-readable media include media in which data can be stored permanently and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.

[0053] The terms used in this document to describe the embodiments of the present disclosure are not intended to limit and / or define the scope of the present disclosure. For example, unless otherwise defined, technical terms or scientific terms used in the present disclosure shall have the ordinary meanings understood by those of ordinary skill in the art to which the present disclosure pertains.

[0054] It should be understood that the terms "first", "second" and similar words used in the present disclosure do not denote any order, quantity or importance, but are only used to distinguish different components. Unless the context clearly dictates otherwise, similar words such as the singular forms "a", "an" or "the" do not denote a limitation of quantity, but rather denote the presence of at least one of the items referred to. For example, a reference to "a component surface" includes a reference to one or more such surfaces.

[0055] As used herein, any reference to "an example" or "examples", "an implementation" or "implementations", "an embodiment" or "embodiments" means that the specific elements, features, structures or characteristics described in connection with that embodiment are included in at least one embodiment. The phrases "in an embodiment" or "in an example" that appear in different places in the specification do not necessarily refer to the same embodiment.

[0056] As used herein, "a part" of something means "at least some" of that thing, and thus may mean less than the whole or the whole of that thing. Thus, "a part" of a thing includes the whole thing as a special case, i.e., the whole thing is an example of a part of the thing.

[0057] It will be further understood that similar words such as the terms "comprise" or "include" mean that the elements or objects appearing before that word cover the listed elements or objects appearing after that word and their equivalents, but do not exclude other elements or objects. Similar words such as "connected" or "being connected" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left" and "right" are only used to express relative positional relationships, and when the absolute position of the object being described changes, the relative positional relationships may change accordingly.

[0058] The various embodiments discussed below for describing the principles of the present disclosure in a patent document are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of the embodiments of the present disclosure will be directed to LTE and / or 5G communication systems, those skilled in the art will understand that the gist of the present disclosure can also be applied, with minor modifications, to other communication systems with similar technical backgrounds and channel formats without departing from the scope of the present disclosure. The technical solutions of the embodiments of the present application can be applied to various communication systems, and for example, the communication system can include Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS) system, Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) system, or New Radio (NR) system, etc. In addition, the technical solutions of the embodiments of the present application can be applied to future-oriented communication technologies. In addition, the technical solutions of the embodiments of the present application can be applied to future-oriented communication technologies.

[0059] The following description with reference to the accompanying drawings helps to comprehensively understand the various embodiments of the present disclosure defined by the claims and their equivalents. It includes various specific details to assist understanding, but these details are only considered exemplary. Therefore, those of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0060] The terms and words used in the following description and claims are not limited to the written meanings, but are used by the inventors only to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of the various embodiments of the present disclosure is for illustrative purposes only and not for the purpose of limiting the present disclosure defined by the appended claims and their equivalents.

[0061] It should be understood that, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" include plural referents. Thus, for example, a reference to "the surface of a component" includes a reference to one or more such surfaces.

[0062] The term "comprises" or "may comprise" means that there are corresponding disclosed functions, operations, or components that can be used in various embodiments of the present disclosure, and does not limit one or more additional functions, operations, or components. Terms such as "comprising" and / or "having" may be interpreted to mean a certain characteristic, quantity, step, operation, component element, component, or a combination thereof, but may not be interpreted to exclude the possibility of the existence or addition of one or more other characteristics, quantities, steps, operation, component elements, components, or a combination thereof.

[0063] The term "or" used in various embodiments of the present disclosure includes any and all combinations of the listed words. For example, the expression "A or B" may include A, may include B, or may include both A and B.

[0064] Unless otherwise defined, all terms (including technical terms or scientific terms) used herein have the same meaning as understood by those skilled in the art to which the present disclosure pertains. Terms defined as in a commonly used dictionary, unless explicitly defined in the present disclosure, should be interpreted as having a meaning equal to the contextual meaning in the relevant field, and should not be interpreted as having an ideal or overly formal meaning.

[0065] According to one aspect of an embodiment of the present disclosure, there is provided a method performed by a second node in a wireless communication system, the method including receiving, from a first node, a first message carrying relevant information of a UE in an RRC inactive state; and performing processing based on the first message.

[0066] According to an embodiment of the present disclosure, the relevant information of a UE in an RRC inactive state includes one of the following: an identifier of the UE; a quantity of the UE; indication information that there is a UE in an RRC inactive state; a session identifier of an MBS to which the UE belongs; status information of the MBS; configuration information of an MBS radio bearer (MRB); a regional scope; indication information on whether a UE in an RRC inactive state is supported to receive MBS services; and indication information on continued retention of MBS context information and / or configuration information.

[0067] According to an embodiment of the present disclosure, the regional scope is a RAN paging scope or a predetermined cell list.

[0068] According to an embodiment of the present disclosure, the second node belongs to the same regional scope as the first node.

[0069] According to an embodiment of the present disclosure, the indication information that there is a UE in an RRC inactive state indicates that there is a UE in an RRC inactive state within the scope of the first node or within the regional scope to which the first node belongs.

[0070] According to an embodiment of the present disclosure, the first message is a UE-specific message.

[0071] According to an embodiment of the present disclosure, the first message is one of the following:

[0072] A message dedicated to MBS multicast; public information.

[0073] According to an embodiment of the present disclosure, the processing includes at least one of the following: the second node maintains UE context information; the second node maintains MBS context information; the second node continues multicast data transmission; the second node does not release the signaling resources and / or user plane resources of the multicast service; the second node does not initiate a multicast context release request message or does not distribute a release command message to the first node.

[0074] According to an embodiment of the present disclosure, the number of UEs in the RRC inactive state is at least 1.

[0075] According to an embodiment of the present disclosure, the UE in the RRC inactive state is at the first node or within the area range to which the first node belongs.

[0076] According to an embodiment of the present disclosure, if the second node is a base station, the processing further includes at least one of the following: sending a request to establish a user plane to the core network; sending a third message carrying relevant information of the UE in the RRC inactive state to a third node; sending a second message carrying relevant information of the UE in the RRC inactive state to the first node.

[0077] According to an embodiment of the present disclosure, the third message includes relevant information of the UE in the RRC inactive state of the second node and / or relevant information of the UE in the RRC inactive state of other receiving nodes.

[0078] According to an embodiment of the present disclosure, the number of other receiving nodes is at least 1.

[0079] According to an embodiment of the present disclosure, the second node receives a response message carrying relevant information of the UE in the RRC inactive state at the third node from the third node.

[0080] According to an embodiment of the present disclosure, the MRB configuration information carried in the response message is the same as the MRB configuration information carried in the third message.

[0081] According to an embodiment of the present disclosure, the second node is a base station, a distributed unit (DU), or a central unit (CU), and the first node is a base station or a central unit (CU).

[0082] According to another aspect of the embodiments of the present disclosure, there is provided a method performed by a second node in a wireless communication system, the method including receiving a first message from a first node, the first message carrying indication information as to whether the first node can enable a UE in RRC Inactive state to receive MBS services; and sending a second message to the first node.

[0083] According to an embodiment of the present disclosure, the second message carries an indication as to whether the second node supports a UE in RRC Inactive state to receive MBS services.

[0084] According to still another aspect of the embodiments of the present disclosure, there is provided a node device in a wireless communication network, including: a transceiver; and a processor coupled to the transceiver and configured to perform the method as described according to the embodiments.

[0085] The main purpose of the embodiments herein is to handle operations in a Standalone Non-Public Network (SNPN).

[0086] Another purpose of the embodiments herein is to handle an emergency call when a UE (with SNPN capability) is onboarded in an SNPN.

[0087] Another purpose of the embodiments herein is to handle the last registered SNPN.

[0088] Another purpose of the embodiments herein is to preferentially select a subscribed SNPN rather than a registered SNPN during an activation process or during an operation in an SNPN access mode process.

[0089] Therefore, the embodiments herein provide a method for handling operations in an SNPN. The method includes the UE determining that the dialed number is an emergency number. Further, the method includes the UE determining that the current SNPN does not support emergency services for the dialed number. Further, the method includes the UE performing a deregistration process when determining that the current SNPN does not support emergency services for the dialed number. Further, the method includes, after performing the deregistration process, the UE selecting at least one of a cell and a Public Land Mobile Network (PLMN) that provides emergency services to the UE.

[0090] In an embodiment, the method includes the UE placing an emergency call over the PS domain when selecting at least one of a cell and a PLMN.

[0091] In an embodiment, the method includes, when selecting at least one of a cell and a PLMN, the UE establishing a Protocol Data Unit (PDU) session for the emergency service. Further, the method includes the UE continuing the emergency service in at least one of the cell and the PLMN.

[0092] In an embodiment, when one of the following occurs, the UE determines that the dialed number is an emergency number: the UE is registered for access service in the SNPN, and the UE is registering for access service in the SNPN.

[0093] In an embodiment, the emergency service includes emergency calls and emergency messages.

[0094] In an embodiment, the deregistration process is one of local deregistration or deregistration with the network.

[0095] Accordingly, embodiments herein provide a method for handling operations in an SNPN. The method includes the UE determining that the UE is in an automatic selection mode. Additionally, the method includes the UE determining the coverage of the subscribed SNPN when determining that the UE is in the automatic selection mode. Additionally, the method includes the UE selecting and registering the subscribed SNPN based on that determination.

[0096] In an embodiment, the method includes, after determining that the coverage of the subscribed SNPN is available, the UE stopping to return one of the registered SNPN and the equivalent SNPN.

[0097] In an embodiment, the UE is in the automatic selection mode when the UE is powered on or the UE starts operating in the SNPN access mode or follows a recovery from lack of coverage, or when the UE changes an entry in the subscriber data list.

[0098] In an embodiment, selecting the subscribed SNPN indicates that the UE selects and registers the subscribed SNPN of the selected entry in the subscriber data list.

[0099] Accordingly, embodiments herein provide a UE that includes an SNPN-based controller coupled to a processor and a memory. The SNPN-based controller is configured to determine that the dialed number is an emergency number. Additionally, the SNPN-based controller is configured to determine that the current SNPN does not support the emergency service for the dialed number. Additionally, the SNPN-based controller is configured to perform a deregistration process when determining that the current SNPN does not support the emergency service for the dialed number. Additionally, the SNPN-based controller is configured to select at least one of a cell and a PLMN that provides emergency service to the UE after performing the deregistration process.

[0100] Accordingly, embodiments herein provide a UE that includes an SNPN-based controller coupled to a processor and a memory. The SNPN-based controller is configured to determine that the UE is in the automatic selection mode. Additionally, the SNPN-based controller is configured to determine the coverage of the subscribed SNPN when determining that the UE is in the automatic selection mode. Additionally, the SNPN-based controller is configured to select and register the subscribed SNPN based on that determination.

[0101] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. However, it should be understood that the following description, while indicating at least one embodiment and many of its specific details, is given by way of illustration and not limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0102] The 3rd Generation Partnership Project (3GPP) network access for a User Equipment (UE) for a Single Network Slice Selection Assistance Information (SNPN) allows the UE to access an Onboarding Network (ONN) to provide the UE with SNPN credentials and other information for primary authentication to enable access to the desired SNPN, i.e., (re)select and (re)register with the SNPN. To provide SNPN credentials in a UE configured with default UE credentials (see Technical Specification (TS) 23.501), the UE selects an SNPN as the ONN and establishes a secure connection with that SNPN, called the Onboarding SNPN (ON-SNPN) (as disclosed in TS 23.501). Based on the ON-SNPN policy, once the UE has registered with the ON-SNPN for onboarding purposes, the Access and Mobility Management Function (AMF) entity may start an implementation-specific timer. The expiration of the timer triggers the AMF entity to deregister the onboarding-registered UE from the ON-SNPN.

[0103] This specific timer is used to prevent an onboarding-registered UE from staying on the ON-SNPN indefinitely. To configure SNPN parameters via the user plane, a UE configured with a Universal Subscriber Identity Module (USIM) with Public Land Mobile Network (PLMN) credentials selects and registers SNPN parameters in the PLMN. After successful registration on the PLMN, SO-SNPN credentials are provided to the UE via the user plane as in TS 23.501. When the onboarding network is a PLMN and the UE's subscription only allows remote provisioning, then based on the PLMN policy, once the UE has registered with the PLMN, the AMF entity may start an implementation-specific timer. The expiration of the timer triggers the AMF entity to deregister the UE from the PLMN. This specific timer is used to prevent a registered UE that is only allowed for remote provisioning from staying at the PLMN indefinitely.

[0104] When the UE has successfully completed the initial registration of the onboarding service in the SNPN, the UE is considered "registered for the onboarding service in the SNPN". Although registered for the onboarding service in the SNPN, services other than the onboarding service are not available.

[0105] When a UE with SNPN capabilities is registered for access services and the user of the UE triggers an emergency call, it is not clarified in the prior art how the UE should handle it, and it may affect emergency services or at least delay the establishment of an emergency call, which is not desirable. The following scenarios may exist:

[0106] 1. Scenario A. The emergency call is supported by the access SNPN, where the UE is registered for access services.

[0107] 2. Scenario B. The access SNPN does not support emergency calls, where the UE is registered for access services.

[0108] 3. Scenario C. The emergency call is supported by the access SNPN, where the UE is registered for access services in the SNPN, but the UE is not allowed to make an emergency call because although it is registered for access services in the SNPN, services other than access services are not available to the UE; that is, the UE is not allowed to utilize other services.

[0109] When the access network is an SNPN, based on the ON-SNPN policy, once the UE has registered with the ON-SNPN for access purposes, the AMF entity can start implementing a specific timer. The expiration of the timer triggers the AMF entity to deregister the access-registered UE from the ON-SNPN that affects emergency services.

[0110] When the access network is a PLMN and the UE's subscription only allows remote provisioning, then based on the PLMN policy, once the UE has registered with the PLMN, the AMF entity can start implementing a specific timer. The expiration of the timer triggers the AMF entity to deregister the UE from the PLMN, thus affecting emergency services.

[0111] The UE enabled for SNPN can operate in the SNPN access mode and can use the credentials from the credential holder to support access to the SNPN. The mobile station (MS) can have several sets of user identifiers, credentials, SNPN identifiers, and other parameters related to SNPN selection. There are two modes of SNPN selection, namely the automatic SNPN selection mode and the manual SNPN selection mode.

[0112] When powering on after recovering from lack of coverage, or when the MS starts operating in the SNPN access mode, the MS uses the new radio - radio access network (NG-RAN) access technology to select the registered SNPN (if the registered SNPN is available). Once the registered SNPN is found on the NG-RAN access technology, the MS in the automatic SNPN selection mode can end the SNPN search process. The MS can select an entry in the "subscriber data list", if any, or the PLMN subscription, if any, for automatic SNPN selection.

[0113] A UE with two or more network subscriptions, where one or more of the network subscriptions can be for a subscribed SNPN, can apply the procedures specified for a multi-USIM UE as described in the 3GPP standard specifications. When the UE registers with the network, the UE can use a separate PEI for each network subscription.

[0114] A UE operating in the SNPN access mode with the automatic SNPN selection mode successfully registers with the SNPN. If the UE restarts or powers on / off, then according to the current specifications, when the same entry in the subscriber data list is selected, the UE can always register with the last registered SNPN.

[0115] In the case where the UE selects the last registered SNPN each time, and according to the current specifications, no high-priority PLMN search is defined, the UE may end up registering on the same (sub-optimal) SNPN at that location, which is incorrect.

[0116] The MS selects the SNPN in the following order (if available and permitted):

[0117] a) The SNPN with which the UE was last registered;

[0118] b) The SNPN identified by the SNPN identifier of the subscribed SNPN in the selected entry of the "subscriber data list" in the ME, if any; and

[0119] c) If the MS supports accessing the SNPN using the credentials of the credential holder, the SNPN selection parameters in the selected entry of the "subscriber data list" or the SNPN selection parameters associated with the selected PLMN subscription.

[0120] Broadcast an indication of support for accessing using the credentials of the credential holder and each SNPN identified (in order of priority) by the SNPN included in the prioritized list of preferred SNPNs controlled by the user.

[0121] Broadcast an indication of support for accessing using the credentials of the credential holder and each SNPN identified (in order of priority) by the SNPN included in the prioritized list of preferred SNPNs controlled by the credential holder;

[0122] Broadcast an indication of support for accessing using the credentials of the credential holder and broadcast the GIN (in order of priority) included in the prioritized GIN list controlled by the credential holder for each SNPN. If more than one such SNPN broadcasts the same GIN, the order in which the MS attempts to register on those SNPNs is MS implementation-specific.

[0123] Each SNPN identified by an SNPN identity that is neither included in the SNPN selection parameters of the entries of the "subscriber data list" nor in the SNPN selection parameters associated with the PLMN subscription does not broadcast a GIN included in the prioritized GIN list controlled by the credential holder, and it broadcasts an indication that SNPN allows registration attempts from an MS not explicitly configured to select the SNPN. If more than one such SNPN is available, the order in which the MS attempts to register on those SNPNs is MS-implementation specific.

[0124] Figure 1 An example flow of events in an existing method when processing the last registered SNPN according to embodiments disclosed herein is shown. At step 1, the UE (100) has registered to a less preferred SNPN (200a) with entry 1 of the subscriber data list in the automatic mode. At step 2, the UE (100) restarts or power cycles or turns the low power mode (LPM) on / off. At step 3, the UE (100) operates in the SNPN access operation mode and performs SNPN selection using the last registered SNPN. At step 4, the UE (100) performs a registration process using the last registered SNPN. At step 5, the UE (100) receives a registration acceptance from the less preferred SNPN (200a). At step 6, whenever the UE (100) powers on / off, if the last registered SNPN is available at that location and the UE (100) has never registered to the preferred SNPN (200b), the same steps are repeated.

[0125] The UE (100) operating in the SNPN access mode with the automatic SNPN selection mode successfully registers to an SNPN. If the UE (100) restarts or powers on / off, according to the current specification, the UE (100) can always start SNPN selection using the last registered SNPN in the selected entry of the subscriber data list.

[0126] In cases where the UE (100) selects the last registered SNPN each time and there is no definition of high-priority PLMN search according to the current specification, the UE (100) may eventually register on the same SNPN (i.e., the less preferred SNPN (200a)) at that location, which is incorrect. This is a key difference when compared with PLMN selection that supports higher-priority PLMN search. Even if the UE registers to the last registered PLMN, the UE can perform a higher-priority PLMN search process when the timer T expires, and the UE can return to the higher-priority PLMN, but no such process is defined for SNPNs that are private networks. Therefore, it is important for the UE to select the correct SNPN when it first starts searching after the power-off and power-on process.

[0127] Figure 2Shows an example flow of events in the existing method when processing the last registered SNPN, depicting the events according to the embodiments disclosed herein. At step 1, the UE (100) has registered the SNPN to entry 1 of the subscriber data list in the automatic mode. At step 2, the UE (100) has entry 2 in the subscriber data list with the last registered SNPN (i.e., the secondary preferred SNPN (200a)). At step 3, the user of the UE (100) selects entry 2 in the subscriber data list in the automatic mode with the subscriber data list having entry 2. At step 4, the UE (100) performs SNPN selection using the last registered SNPN in entry 2 of the subscriber data list. At step 5, the UE (100) transmits a registration request to the last registered SNPN. At step 6, the UE (100) receives a registration acceptance from the last registered SNPN based on the registration request. At step 7, even if the preferred SNPN (200b) exists at this location, the UE (100) never selects the preferred SNPN (200b) because the UE (100) always registers to the last registered SNPN.

[0128] The above is illustrated by switching the subscription between entries of the subscriber data list. That is, from entry - 1 of the subscriber data list to entry - 2 of the subscriber data list. The same concept applies when there is a subscription switch between the USIM and the entries of the subscriber data list, and vice versa.

[0129] The UE (100) having two or more network subscriptions can apply the procedures specified for multi - USIM UEs described in the 3GPP standard specifications, where one or more network subscriptions can be used for the subscribed SNPN. When the UE registers to the network, the UE (100) can use a separate PEI for each network subscription.

[0130] The UE (100) operating in the SNPN access mode with the automatic SNPN selection mode successfully registers to the SNPN (using entry 1 of the subscriber data list & PEI - 1). If the user of the UE (100) selects a different entry of the subscriber data list (e.g., entry 2 of the subscriber data list with PEI - 1 or entry 1 of the subscriber data list with PEI - 1 or entry 2 of the subscriber data list with PEI - 2) PEI, then according to the current specification, the UE (100) can always start SNPN selection using the last registered SNPN in the selected entry of the subscriber data list.

[0131] In the case where the UE (100) selects the last registered SNPN from the selected entries in the subscriber data list each time, and according to the current specification, no high-priority PLMN search is defined, the UE (100) may eventually register on the same SNPN (i.e., the second-preferred SNPN (200a)) at that location, which is incorrect.

[0132] Accordingly, it is desirable to address one or more of the above disadvantages or other disadvantages and at least provide a useful alternative.

[0133] Reference is made to the non-limiting embodiments shown in the accompanying drawings and detailed in the following description to more fully explain the embodiments herein and their various features and advantageous details. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments herein. The examples used herein are only intended to facilitate an understanding of the manner in which the embodiments herein can be practiced and further enable those skilled in the art to practice the embodiments herein. Therefore, the examples should not be construed as limiting the scope of the embodiments herein.

[0134] For the purpose of interpreting this specification, definitions (as defined herein) may be applied and, where appropriate, terms used in the singular will also include the plural and vice versa. It should be understood that the terms used herein are for the purpose of describing particular embodiments only and are not limiting. Unless otherwise stated, the terms "comprising", "having" and "including" should be construed as open-ended terms.

[0135] The words / phrases "exemplary", "instance", "illustrative", "in an instance", "etc.", "for example", "i.e." are used herein only to mean "serving as an example, instance or illustration". Any embodiment or implementation of the subject matter described using the words / phrases "exemplary", "example", "illustrative", "in an instance", "etc.", "for example", "i.e." herein is not necessarily to be construed as being preferred or advantageous over other embodiments.

[0136] Embodiments herein may be described and illustrated in terms of blocks that perform one or more of the described functions. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., are physically implemented by analog and / or digital circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware. The circuitry may be embodied, for example, in one or more semiconductor chips or in a substrate support such as a printed circuit board. The circuitry constituting the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware implementing some functions of the block and a processor implementing other functions of the block. Without departing from the scope of the present disclosure, each block of an embodiment may be physically divided into two or more interacting and discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of an embodiment may be physically combined into more complex blocks.

[0137] It should be noted that the elements in the drawings are shown for purposes of this description and for ease of understanding, and may not necessarily be drawn to scale. For example, the flowcharts / sequence diagrams show the method in terms of the steps required to understand aspects of the embodiments disclosed herein. Additionally, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details relevant to understanding the present embodiments so as not to obscure the drawings with details that would be readily apparent to a person of ordinary skill in the art benefiting from the description herein. Additionally, in terms of the system, including one or more components / modules of the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details relevant to understanding the present embodiments so as not to obscure the drawings with details that would be readily apparent to a person of ordinary skill in the art benefiting from the description herein.

[0138] The drawings are used to facilitate easy understanding of the various technical features, and it should be understood that the embodiments presented herein are not limited by the drawings. Accordingly, the present disclosure should be construed as extending to any modifications, equivalents, and alternatives other than those specifically set forth in the drawings and the corresponding description. The use of words such as first, second, third, etc. to describe components / elements / steps is for purposes of this description and should not be construed as denoting sequential ordering / placement / appearance unless otherwise stated.

[0139] The terms UE and MS may be used interchangeably in this embodiment and have the same meaning. The terms power on and turn on may be used interchangeably in this embodiment and have the same meaning. The terms power off and turn off may be used interchangeably in this embodiment and have the same meaning.

[0140] The following definitions and abbreviations are mentioned herein:

[0141] UE: User Equipment;

[0142] NW: Network;

[0143] SNPN: Standalone Non-Public Network;

[0144] PLMN: Public Land Mobile Network;

[0145] AMF entity: Access and Mobility Management Function entity;

[0146] ON-SNPN: On-Network Standalone Non-Public Network;

[0147] PLMN: Public Land Mobile Network;

[0148] USIM: Universal Subscriber Identity Module; and

[0149] PEI: Permanent Equipment Identifier.

[0150] Embodiments herein implement a method for handling operations in an SNPN. The method includes the UE determining that the dialed number is an emergency number. Additionally, the method includes the UE determining that the current SNPN does not support emergency services for the dialed number. Additionally, the method includes the UE performing a local deregistration process when it is determined that the current SNPN does not support emergency services for the dialed number. Additionally, the method includes the UE selecting at least one of a cell and a PLMN that provides emergency services to the UE after performing the deregistration process.

[0151] When a UE (with SNPN capabilities) accesses in a Standalone Non-Public Network (SNPN), the proposed method can be used to handle emergency calls. The proposed method allows the UE to handle emergency calls while being registered for on-network services in the SNPN. The proposed method allows the UE to handle emergency calls while being registered for on-network services, which is a state where the UE is not allowed to have other services.

[0152] The UE selects and registers in the subscribed SNPN of an entry in the "Subscriber Data List" rather than the last registered SNPN. This gives the UE a new mechanism to select a higher-priority SNPN over the registered SNPN when powering on, after service restoration, and when the UE starts operating in the SNPN access operation mode.

[0153] Now referring to the drawings, and more particularly to Figures 3 to 12 , which shows at least one embodiment, where like reference numerals consistently denote corresponding features in all the drawings.

[0154] Figure 3Fig. 0 shows an example scenario for enabling a UE (100) to make an emergency call according to an embodiment disclosed herein, where the UE (100) is currently unable to make an emergency call in an ON-SNPN. The UE (100) can be, for example but not limited to, a laptop computer, a smart phone, a desktop computer, a notebook, a device-to-device (D2D) device, a vehicle-to-everything (V2X) device, a foldable phone, a smart TV, a tablet computer, an immersive device, and an Internet of Things (IoT) device.

[0155] At least one of the following steps is performed by the UE (100) in any combination for one or more situations described in this embodiment, or generally whenever the UE (100) triggers an emergency call when being registered or in the process of registering for access services:

[0156] a) The UE (100) may perform SNPN selection or PLMN selection, cell selection or cell reselection as specified in TS 23.122 to select a PLMN or SNPN or cell / tracking area identity (TAI) that can provide emergency services to the UE (100) (i.e., a network that supports the UE's emergency services). This may cause the UE (100) to leave the currently registered SNPN. When selecting an appropriate PLMN or SNPN, the UE (100) triggers a non-access stratum (NAS) procedure; for example, a registration procedure for 5GS registration type "emergency registration" to register for emergency services;

[0157] b) Perform a deregistration procedure. The UE may perform the deregistration procedure by itself (also known as locally) or optionally with the network to indicate to the AMF entity (300) that the UE (100) is no longer registered for access services;

[0158] c) Deactivate the SNPN access mode. In this case, the UE (100) may perform SNPN selection or PLMN selection, cell (re)selection according to TS 23.122.38.331, 38.304 to select a PLMN that supports emergency services. After successfully registering (optionally, registering for emergency services) in the PLMN or SNPN, the UE (100) may establish a PDU for emergency services and continue the emergency call in the PLMN;

[0159] d) The UE (100) may abort an ongoing access process; for example, the UE (100) may not initiate a PDU establishment process for remote provision of SNPN parameters. Or, if an access PDU has been established, the UE (100) may not continue the remote provision of SNPN parameters and optionally release the access PDU or not continue to establish user plane resources to download provisioning information, etc.;

[0160] e) The UE (100) may trigger a NAS procedure; for example, the registration procedure with a 5GS registration type is "emergency registration" to indicate to the AMF entity (300) that the UE (100) is no longer registered for access network services; that is, it switches from the registered access network services to emergency services. Optionally, once an acknowledgement is received from the network; for example, as an indication in a registration acceptance message or a NAS message, the UE (100) registers for emergency services in one of the NAS messages, and the UE (100) may start the procedure for establishing an emergency call; for example, by initiating the establishment of an emergency PDU session;

[0161] f) When the UE (100) attempts to establish a PDU session for emergency services (e.g., establishing or in the process of establishing a PDU session for emergency services), or if the UE (100) triggers the registration of an emergency service procedure or any NAS procedure related to emergency services, after the UE (100) is registered for access network (or for the cases described in TS 24.501), the implementation-specific timer for access network services initiated by the AMF entity (300) is stopped;

[0162] g) Once the UE (100) starts the procedure for an emergency call, e.g., establishing a PDU session for emergency services, the implementation-specific timer at the AMF entity (300) is paused. After releasing the emergency call or emergency service (e.g., releasing the PDU session for emergency services), the AMF entity (300) may (re)start the timer or start the timer. Optionally, this applies when the UE (100) starts an emergency call in the same SNPN or PLMN where the UE is registered for access network services; and

[0163] h) Even after successfully establishing a PDU for emergency services, the AMF entity (300) is allowed to continue and run the implementation-specific timer started after the UE (100) was successfully registered for access network services. If the timer expires during an ongoing emergency call or during the emergency service, the AMF entity (300) may not deregister the UE (100). Optionally, the AMF entity (300) may send a configuration update command to the UE (100) indicating that it is "registered for emergency services". The UE (100) may remain registered for emergency services as described in TS 24.501.

[0164] When the UE (100) performs an initial registration for access network services in the SNPN, e.g., when the UE (100) indicates "SNPN access network registration" in the 5GS registration type IE, the UE (100) is registered for access network services.

[0165] It performs a deregistration procedure with the ON-SNPN to indicate that it is no longer registered for access services. Then, the UE (100) performs SNPN selection to find an SNPN that supports emergency services, establishes an emergency PDU, and continues to place an emergency call in that SNPN.

[0166] In step 1, the UE (100) is in the SNPN access mode and is registered for access services. In step 2, the user of the UE (100) triggers an emergency call. In step 3, the UE (100) optionally transmits a deregistration request to the SNPN-A. In step 4, the AMF entity (300) stops the access timer. In step 5, the AMF entity (300) transmits a deregistration acceptance to the UE (100). In step 6, the UE (100) performs SNPN selection according to TS 23.122 to find an SNPN that supports the emergency situation. In step 7, the UE (100) finds an SNPN-B that supports emergency services. In step 8, the UE (100) transmits a registration request in the SNPN-B, where the 5GS registration type is "emergency registration". In step 9, the UE (100) receives a registration acceptance from the AMF entity (300).

[0167] In step 10, the UE (100) transmits a PDU session establishment request for emergency PDU establishment to the SMF entity (400). In step 11, the UE (100) receives a PDU session establishment acceptance for emergency PDU establishment from the SMF entity (400). In step 12, an emergency call is placed in the SNPN-B at the UE (100).

[0168] Figure 4 An example scenario for enabling the UE (100) to place an emergency call according to an embodiment disclosed herein is shown, where the UE (100) currently cannot place an emergency call in the ON-SNPN. It performs a deregistration procedure with the ON-SNPN to indicate that it is no longer registered for access services. The deregistration procedure can be local, or it can optionally be indicated to the network by transmitting a deregistration message. Then, the UE (100) deactivates the SNPN access mode, performs PLMN selection to find a PLMN that supports emergency services, and continues to place an emergency call in that PLMN.

[0169] In step 1, the UE (100) is in the SNPN access mode and is registered for network access services in SNPN-A. In step 2, the user of the UE (100) triggers an emergency call. In step 3, optionally, the UE (100) transmits a deregistration request to SNPN-A. In step 4, the AMF entity (300) stops the network access timer. In step 5, the AMF entity (300) transmits a deregistration acceptance message to the UE (100). In step 6, the UE (100) deactivates the SNPN access mode and performs PLMN selection according to TS 23.122 to find a PLMN that supports emergency services.

[0170] In step 7, the UE (100) finds a PLMN-A that supports emergency services. In step 8, the UE (100) transmits a registration request in PLMN-A, where the 5GS registration type is "emergency registration". In step 9, the AMF entity (300) transmits a registration acceptance to the UE (100). In step 10, the UE (100) transmits a PDU session establishment request for emergency PDU establishment to the SMF entity (400). In step 11, the SMF entity (400) transmits a PDU session establishment acceptance for emergency PDU establishment to the UE (100). In step 12, an emergency call is dialed in the PLMN at the UE (100).

[0171] Figure 5 An example scenario for enabling the UE (100) to make an emergency call according to an embodiment disclosed herein is shown, where the UE (100) currently cannot make an emergency call in the ON-SNPN because the SNPN does not support emergency services. The UE (100) performs deregistration in the ON-SNPN. The deregistration process can be completed locally in the UE or indicate to the network and find another suitable SNPN that supports the emergency situation, and make an emergency call after the emergency PDU is established.

[0172] In step 1, the UE (100) is in the SNPN access mode and is registered for the network access service. In step 2, the user of the UE (100) triggers an emergency call. In step 3, the UE (100) optionally transmits a deregistration request to the SNPN-A or performs a local deregistration process, i.e., typically the UE performs a deregistration process. In step 4, the AMF entity (300) stops the network access timer. In step 5, the AMF entity (300) transmits a deregistration acceptance to the UE (100). In step 6, the UE (100) performs SNPN selection according to TS 23.122 to find an SNPN that supports emergency situations. In step 7, the UE (100) finds an SNPN-B that supports emergency services. In step 8, the UE (100) transmits a registration request with the 5GS registration type of "emergency registration" to the AMF entity (300) in the SNPN-B. In step 9, the AMF entity (300) transmits a registration acceptance to the UE (100). In step 10, the UE (100) transmits a PDU session establishment request for emergency PDU establishment to the SMF entity (400). In step 11, the SMF entity (400) transmits a PDU session establishment acceptance for emergency PDU establishment to the UE (100). In step 12, an emergency call is made in the SNPN-B at the UE (100).

[0173] Figure 6 An example scenario is shown where the UE (100) continues to make an emergency call in the same ON-SNPN that supports emergency services. When the UE (100) initiates a PDU for emergency services and makes an emergency call after successfully establishing the PDU, the AMF entity (300) stops the network access timer.

[0174] In step 1, the UE (100) is in the SNPN access mode. In step 2, the UE (100) transmits a registration request in the SNPN-A to the AMF entity (300), where the 5GS registration type is "SNPN network access registration". In step 3, the UE (100) receives a registration acceptance from the AMF entity (300). In step 4, the AMF entity (300) starts the network access timer. In step 5, the UE (100) is registered for the network access service in the SNPN-A. In step 6, the user of the UE (100) triggers an emergency call. In step 7, the UE (100) chooses to make an emergency call in the same SNPN and establish an emergency PDU.

[0175] In step 8, the UE (100) transmits a PDU session establishment request for emergency PDU establishment to the SMF entity (400). In step 9, the AMF entity (300) stops the access network timer. In step 10, the SMF entity (400) transmits a PDU session establishment acceptance for emergency PDU establishment to the UE (100). In step 11, an emergency call is placed in the SNPN-A at the UE (100).

[0176] Figure 7 An example scenario is shown where the UE (100) continues to place an emergency call in the same ON-SNPN that supports emergency services. When the UE (100) initiates a PDU for emergency services and the UE (100) places an emergency call after successful PDU establishment, the AMF entity (300) continues to run the access network timer. When the timer expires, the AMF entity (300) does not deregister the UE (100), and the AMF entity (300) transmits a UE (100) configuration update command to indicate to the UE (100) to "register for emergency services".

[0177] In step 1, the UE (100) is in SNPN access mode. In step 2, the UE (100) transmits a registration request in the SNPN-A to the AMF entity (300), where the 5GS registration type is "SNPN access network registration". In step 3, the UE (100) receives a registration acceptance from the AMF entity (300). In step 4, the AMF entity (300) starts the access network timer. In step 5, the UE (100) is registered for access network services in the SNPN-A. In step 6, the user of the UE (100) triggers an emergency call. In step 7, the UE (100) selects to place an emergency call in the same SNPN and establish an emergency PDU.

[0178] In step 8, the UE (100) transmits a PDU session establishment request for emergency PDU establishment to the SMF entity (400). In step 9, the AMF entity (300) continues to run the access network timer. In step 10, the SMF entity (400) transmits a PDU session establishment acceptance for emergency PDU establishment to the UE (100). In step 11, an emergency call is placed in the SNPN-A at the UE (100). In step 12, during an ongoing call at the AMF entity (300) and the SMF entity (400), the access network timer expires. In step 13, the AMF entity (300) transmits a configuration update command to the UE (100) indicating that the AMF entity (300) "registers for emergency services". In step 14, the UE (100) continues the ongoing emergency call in the SNPN-A. The UE (100) believes itself to be registered for emergency services.

[0179] Figure 8A flowchart is shown that illustrates an exemplary method for a UE (100) to process the last registered SNPN according to embodiments disclosed herein. A UE (100) operating in SNPN access mode may select an SNPN in the following order (i.e., the term preferred SNPN (200b) is the highest priority available SNPN following the following priority order) if the SNPN is available (i.e., the coverage of the corresponding SNPN is found) and is admissible:

[0180] 1. The SNPN identified by the SNPN identifier of the subscribed SNPN in the selected entry of the "subscriber data list" in the ME, if any;

[0181] 2. If the MS supports accessing the SNPN using the credentials of the credential holder, use the SNPN selection parameter in the selected entry of the "subscriber data list" or the SNPN selection parameter associated with the selected PLMN subscription:

[0182] 1) Each SNPN that broadcasts an indication of support for accessing using the credentials of the credential holder and is identified by the SNPN identifier included in the list of user-controlled prioritized preferred SNPNs (in priority order),

[0183] 2) Each SNPN that broadcasts an indication of support for accessing using the credentials of the credential holder and is identified by the SNPN identifier included in the list of credential-holder-controlled prioritized preferred SNPNs (in priority order),

[0184] 3) Each SNPN that broadcasts an indication of support for accessing using the credentials of the credential holder and broadcasts the GIN included in the list of credential-holder-controlled prioritized GINs (in priority order). If more than one such SNPN broadcasts the same GIN, the order in which the MS attempts to register on those SNPNs is MS-implementation specific, and

[0185] 4) Each SNPN identified by the SNPN identifier that is neither included in the SNPN selection parameter of the entry in the "subscriber data list" nor included in the SNPN selection parameter associated with the PLMN subscription, that does not broadcast the GIN included in the list of credential-holder-controlled prioritized GINs, and that broadcasts an indication that the SNPN allows registration attempts from an MS not explicitly configured to select an SNPN. If more than one such SNPN is available, the order in which the MS attempts to register on those SNPNs is MS-implementation specific; and.

[0186] 3. Optionally, the SNPN to which the UE (100) last registered.

[0187] In an embodiment, after power-on / activation of the UE (100) or when the MS starts operating in the SNPN access operation mode, the UE can perform SNPN selection and select a preferred SNPN (200b). As Figure 8 described, in step 1, the UE (100) has registered to a secondary preferred SNPN (200a) using a selected entry 1 of the subscriber data list in the automatic mode. In step 2, the UE (100) restarts or performs a power-on / off cycle or a low-power mode (LPM) on / off, or the MS starts operating in the SNPN access operation mode. In step 3, the UE (100) operates in the SNPN access operation mode and always performs SNPN selection using the preferred SNPN (200b). In step 4, the UE (100) transmits a registration request to the preferred SNPN (200b). In step 5, the UE (100) receives a registration acceptance from the preferred SNPN (200b) based on the registration request. In step 6, the UE (100) is registered to the preferred SNPN (200b) at that location. That is, in this case, the UE (100) can ignore the last registered SNPN (i.e., the ME may not return to the registered SNPN or an equivalent SNPN).

[0188] Figure 9 A flowchart showing an exemplary call flow when processing the last registered SNPN according to an embodiment disclosed herein is shown. In Figure 9 this case, after the user of the UE (100) selects a different entry in the subscriber data list, the UE (100) can perform SNPN selection using the preferred SNPN list as follows.

[0189] For each case of selecting a new entry in the subscriber data list, the UE (100) can have the option to ignore the last registered SNPN and start SNPN selection using the preferred SNPN list such that at least once the UE (100) attempts the preferred SNPN.

[0190] In step 1, the UE (100) has registered with the SNPN in automatic mode using entry 1 of the subscriber data list. In step 2, the UE (100) enters 2 in the subscriber data list with the last registered SNPN (sub-preferred SNPN) (200a). In step 3, the user of the UE (100) selects entry 2 in the subscriber data list in automatic mode. In step 4, the UE (100) may ignore the last registered SNPN in entry 2 of the subscriber data list and perform SNPN selection using the preferred SNPN list. In step 5, the UE (100) performs the registration process using the preferred SNPN (200b). In step 6, the UE (100) receives a registration acceptance from the preferred SNPN (200b) based on the registration process. In step 7, the UE (100) with the new list of subscriber data selected by the user always registers to the preferred allowable available SNPN.

[0191] In an embodiment, the UE (100) includes two or more network subscriptions, one or more of which can be used for the subscribed SNPN, and the procedures specified for multi-USIM UEs as described in the 3GPP standard specifications can be applied. When the UE registers to the network, the UE (100) can use a separate PEI for each network subscription.

[0192] After a power cycle, the last registered SNPN can be selected only if the selected entry of the list of subscriber data + PEI (optionally, if there are multiple PEIs, the selected PEI) is the same as before the power cycle (i.e., off and on).

[0193] If the entry of the selected subscriber data list or PEI (optionally, the selected PEI if there are multiple PEIs) is different, the UE (100) can start the SNPN selection with the preferred SNPN list that ignores the last registered SNPN in the entry of the subscriber data list.

[0194] In an embodiment, if the MS is in the automatic SNPN selection mode and the MS finds the coverage of the subscribed SNPN or the preferred SNPN (200b), the MS may register to the subscribed SNPN or the preferred SNPN (200b) and not return to the registered SNPN or the equivalent SNPN. Optionally, the operator may be able to control whether to allow the MSs that support this option to perform this alternative behavior through the SIM configuration or the configuration in the ME. That is to say, a flag / indication / information element may be configured in the UE (100) (in the ME or USIM), and the flag / indication / information element indicates to the UE (100) that the UE may select the last registered SNPN or the preferred SNPN (200b) / subscribed SNPN when it is turned on or resumes from lack of coverage or when the UE (100) starts to operate in the SNPN access mode or when the UE (100) selects another entry in the subscriber data list.

[0195] The flag may be configured in the UE (100) by using the UE parameter update procedure (see TS 23.501 / TS 23.502) or using the UE configuration update procedure (see TS 23.501 / TS 23.502) or the guidance of the roaming procedure, through any one of the NAS messages / NAS procedures or through the data path or by using the OTA mechanism (MO data) or SMS or any other mechanism. For illustration, the following example may be considered.

[0196] The flag name may be ShouldRegSNPN-prioritized.

[0197] 1. Value 0: Indicates to the UE (100) that the UE may not select (lower the priority) the last registered SNPN, even if it is available. Optionally, for all cases described in this embodiment, and select the subscribed SNPN or the preferred SNPN (200b).

[0198] 2. Value 1: Indicates to the UE (100) that the UE may select the last registered SNPN with priority (if available). Optionally, for all cases described in this embodiment.

[0199] 3. The flag is configured according to each entry in the subscriber data list.

[0200] In an embodiment, the term "not select" or "ignore" implies that the UE (100) may first attempt to select the preferred SNPN (200b) in the order of priority. In other words, the UE (100) may start the SNPN selection, ignoring the information of the last registered SNPN that maintains the priority of all other SNPNs.

[0201] In the example, the UE (100) is configured with the last registered SNPN (i.e., SNPN-3) and the subscribed SNPN (i.e., SNPN-1). The prioritized preferred SNPN list controlled by the credential holder (in priority order): SNPN-2, SNPN-3, SNPN-4. If SNPN-1 is available, the UE (100) can select SNPN-1, ignoring the last registered SNPN-3. If SNPN-1 is not available but SNPN-2 is available, the UE (100) can select SNPN-2. If neither SNPN-1 nor SNPN-2 is available but SNPN-3 is available, the UE (100) can select SNPN-3. That is, the UE (100) can ignore the later registered SNPN information and follow the priority order configured in the UE (100).

[0202] Figure 10 Shows various hardware components of the UE (100) according to embodiments disclosed herein. In an embodiment, the UE (100) includes a processor (110), a communicator (120), a memory (130), and an SNPN-based controller (140). The processor (110) is coupled to the communicator (120), the memory (130), and the SNPN-based controller (140).

[0203] The SNPN-based controller (140) determines that the dialed number is an emergency number. In an embodiment, the UE (100) determines that the dialed number is an emergency number in one of the following cases: the UE (100) is registered for access services in the SNPN, and the UE (100) is being registered for access services in the SNPN. In addition, the SNPN-based controller (140) determines that the current SNPN does not support the emergency service for the dialed number. The emergency service can be, for example but not limited to, an emergency call and an emergency message. In addition, the SNPN-based controller (140) performs a deregistration process when determining that the current SNPN does not support the emergency service for the dialed number. The deregistration process is one of a local deregistration or a deregistration with the network. In addition, the SNPN-based controller (140) selects at least one of a cell and a PLMN that provides emergency services to the UE (100) after performing the deregistration process.

[0204] In an embodiment, when selecting at least one of a cell and a PLMN, the SNPN-based controller (140) dials the emergency service over the PS domain.

[0205] In another embodiment, the SNPN-based controller (140) sets a PDU for the emergency service when selecting at least one of a cell and a PLMN. The SNPN-based controller (140) continues the emergency service in at least one of the cell and the PLMN.

[0206] In an embodiment, an SNPN-based controller (140) determines that a UE (100) is in an automatic selection mode. In an embodiment, the UE (100) is in the automatic selection mode when the UE (100) is powered on or the UE (100) starts operating in an SNPN access mode, or after recovering from a lack of coverage, or when the UE (100) changes an entry in a subscriber data list. Further, the SNPN-based controller (140) determines a coverage of a subscribed SNPN when determining that the UE (100) is in the automatic selection mode. Further, the SNPN-based controller (140) selects and registers the subscribed SNPN based on the determination. In an embodiment, selecting the subscribed SNPN indicates that the UE (100) selects and registers the subscribed SNPN of a selected entry in the subscriber data list. Further, the SNPN-based controller (140) stops returning one of a registered SNPN and an equivalent SNPN after determining that the coverage of the subscribed SNPN is available.

[0207] The SNPN-based controller (140) is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc., and may optionally be driven by firmware.

[0208] The processor (110) may include one or more processors. The one or more processors may be general-purpose processors (such as a central processing unit (CPU), an application processor (AP), etc.), a graphics processing unit only (such as a graphics processing unit (GPU), a vision processing unit (VPU)), and / or an AI dedicated processor (such as a neural processing unit (NPU)). The processor (110) may include multiple cores and be configured to execute instructions stored in the memory (130).

[0209] In addition, the processor (110) is configured to execute instructions stored in the memory (130) and perform various processes. The communicator (120) is configured to perform internal communication between internal hardware components and internal communication with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical discs, floppy disks, flash memories, or forms of electrically programmable read-only memory (EPROM) or electrically erasable programmable (EEPROM) memory. Additionally, in some examples, the memory (130) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagated signal. However, the term "non-transitory" should not be construed to mean that the memory (130) is immovable. In certain instances, the non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or cache memory).

[0210] Although Figure 10 Although various hardware components of the UE (100) are shown, it should be understood that other embodiments are not limited thereto. In other embodiments, the UE (100) may include fewer or greater numbers of components. Additionally, the labeling or naming of the components is for illustrative purposes only and does not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions in the UE (100).

[0211] Figure 11 A flowchart of a method for processing an emergency service during network access in an SNPN while processing operations in the SNPN according to embodiments disclosed herein is shown. Operations (1102-1108) are processed by an SNPN-based controller (140).

[0212] In step 1102, the method includes determining that the dialed number is an emergency number. In step 1104, the method includes determining that the current SNPN does not support the emergency service for the dialed number. In step 1106, the method includes performing a deregistration process when it is determined that the current SNPN does not support the emergency service for the dialed number. In step 1108, the method includes selecting a cell and a PLMN that provide emergency services to the UE (100) after performing the deregistration process.

[0213] The proposed method allows the UE (100) to process an emergency call while being registered for network access services in the SNPN. The proposed method allows the UE (100) to process an emergency call while being registered for network access services, which is not allowed for other services of the UE (100).

[0214] Figure 12A flowchart of a method for processing operations in an SNPN while processing the last registered SNPN according to embodiments disclosed herein is shown. Operations (1202 - 1206) are processed by an SNPN-based controller (140).

[0215] In step 1202, the method includes determining that the UE (100) is in the automatic selection mode. In step 1204, the method includes determining the coverage of the subscribed SNPN when it is determined that the UE (100) is in the automatic selection mode. In step 1206, the method includes selecting and registering the subscribed SNPN based on the determination.

[0216] Based on the proposed method, the UE selects and registers in the subscribed SNPN of an entry in the "subscriber data list" rather than the last registered SNPN. This gives the UE a new mechanism to select a higher-priority SNPN over the registered SNPN when powering on, after service restoration, and when the UE starts operating in the SNPN access operation mode.

[0217] The method can also be implemented in a wireless network, which can be, for example but not limited to, a fourth-generation (4G) network, a fifth-generation (5G) network, an open radio access network (ORAN), etc.

[0218] The various actions, operations, blocks, steps, etc. in the flowcharts (1100 and 1200) can be executed in the presented order, in a different order, or simultaneously. Additionally, in some embodiments, some of the actions, operations, blocks, steps, etc. can be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0219] The embodiments disclosed herein can be implemented by at least one software program running on at least one hardware device and performing network management functions to control elements. The elements can be at least one of a hardware device or a combination of a hardware device and software modules.

[0220] The foregoing description of specific embodiments will so fully disclose the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt such specific embodiments for various applications without departing from the general concept, and thus, such adaptations and modifications should and are intended to be understood as being within the meaning and range of equivalents of the disclosed embodiments. It should be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Thus, although the embodiments herein have been described in accordance with at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the spirit and scope of the embodiments as described herein.

[0221] Figure 13The structure of a UE to which embodiments of the present disclosure can be applied is shown.

[0222] Refer to Figure 13 , the UE includes a radio frequency (RF) processor 1310, a baseband processor 1320, a storage unit 1330, and a controller 1340.

[0223] The RF processor 1310 performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and signal amplification. That is, the RF processor 1310 up-converts the baseband signal provided from the baseband processor 1320 into an RF band signal, transmits the RF band signal through an antenna, and then down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1310 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Although Figure 13 only one antenna is shown, the UE may include multiple antennas. In addition, the RF processor 1310 may include multiple RF chains. In addition, the RF processor 1310 may perform beamforming. For beamforming, the RF processor 1310 may control the phase and magnitude of each signal transmitted / received through multiple antennas or antenna elements. The RF processor may perform MIMO and receive multiple layers when performing the MIMO operation. The RF processor 1310 may appropriately configure multiple antennas or antenna elements according to the control of the controller to perform receive beam scanning or control the direction and beam width of the receive beam so that the receive beam corresponds to the transmit beam.

[0224] The baseband processor 1320 performs a function for converting between a baseband signal and a bit stream according to the physical layer standard of the system. For example, when transmitting data, the baseband processor 1320 generates complex symbols by encoding and modulating the transmit bit stream. In addition, when receiving data, the baseband processor 1320 reconstructs the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1310. For example, in an orthogonal frequency division multiplexing (OFDM) scheme, when transmitting data, the baseband processor 1320 generates complex symbols by encoding and modulating the transmit bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 1320 divides the baseband signal provided from the RF processor 1310 in units of OFDM symbols, reconstructs the signal mapped to the subcarriers through a fast Fourier transform (FFT) operation, and then reconstructs the received bit stream by demodulating and decoding.

[0225] The baseband processor 1320 and the RF processor 1310 transmit and receive signals as described above. Thus, the baseband processor 1320 and the RF processor 1310 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. In addition, at least one of the baseband processor 1320 and the RF processor 1310 may include multiple communication modules to support a variety of different radio access technologies. In addition, at least one of the baseband processor 1320 and the RF processor 1310 may include different communication modules to process signals of different frequency bands. For example, different radio access technologies may include an LTE network and an NR network. In addition, different frequency bands may include super high frequency (SHF) (e.g., 2.5 GHz and 5 GHz) bands and millimeter (mm) wave (e.g., 60 GHz) bands.

[0226] The storage unit 1330 stores data such as basic programs, applications, and setting information for the operation of the UE. The storage unit 1330 provides the stored data in response to a request from the controller 1340.

[0227] The controller 1340 controls the overall operation of the UE. For example, the controller 1340 transmits / receives signals through the baseband processor 1320 and the RF processor 1310. In addition, the controller 1340 may record data in the storage unit 1330 and read data. To this end, the controller 1340 may include at least one processor. For example, the controller 1340 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls a high layer such as an application program.

[0228] Figure 14 A block diagram of a base station in a wireless communication system according to an embodiment disclosed herein is shown.

[0229] As Figure 14 As illustrated in the figure, the base station includes an RF processor 1410, a baseband processor 1420, a backhaul communication unit 1430, a storage unit 1440, and a controller 1450.

[0230] The RF processor 1410 performs functions for transmitting and receiving signals through a wireless channel, such as frequency band conversion and signal amplification. That is, the RF processor 1410 up-converts the baseband signal provided from the baseband processing unit 1420 into an RF band signal and then transmits the converted signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1410 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although Figure 14Only one antenna is shown, but the first access node may include multiple antennas. In addition, the RF processor 1410 may include multiple RF chains. In addition, the RF processor 1410 may perform beamforming. For beamforming, the RF processor 1410 may control the phase and magnitude of each signal transmitted and received through the multiple antennas or antenna elements. The RF processor may perform downlink MIMO operations by transmitting one or more layers.

[0231] The baseband processor 1420 performs the function of converting between baseband signals and bitstreams according to the physical layer standards of the first radio access technology. For example, when transmitting data, the baseband processor 1420 generates complex symbols by encoding and modulating the transmitted bitstream. In addition, when receiving data, the baseband processor 1420 reconstructs the received bitstream by demodulating and decoding the baseband signal provided by the RF processor 1410. For example, in the OFDM scheme, when transmitting data, the baseband processor 1420 may generate complex symbols by encoding and modulating the transmitted bitstream, map the complex symbols to subcarriers, and then configure OFDM symbols through IFFT operations and CP insertion. Additionally, when receiving data, the baseband processor 1420 divides the baseband signal provided by the RF processor 1410 in units of OFDM symbols, recovers the signal mapped by the subcarriers through FFT operations, and then recovers the received bitstream through demodulation and decoding. The baseband processor 1420 and the RF processor 1410 transmit and receive signals as described above. Therefore, the baseband processor 1420 and the RF processor 1410 may be referred to as transmitters, receivers, transceivers, or communication units.

[0232] The communication unit 1430 provides an interface for communicating with other nodes within the network.

[0233] The storage unit 1440 stores data such as basic programs, applications, and setting information for the operation of the MeNB. Specifically, the storage unit 1440 may store information about the bearers allocated to the accessed UEs and the measurement results reported by the accessed UEs. Further, the storage unit 1440 may store information about the reference for determining whether to provide multiple connections to the UEs or to stop multiple connections. In addition, the storage unit 1440 provides the data stored therein according to a request from the controller 1450.

[0234] The controller 1450 controls the overall operation of the MeNB. For example, the controller 1450 transmits and receives signals through the baseband processor 1420 and the RF processor 1410 or through the backhaul communication unit 1430. In addition, the controller 1450 may record data in the storage unit 1440 and read the data. To this end, the controller 1450 may include at least one processor.

[0235] Figure 15 A diagram showing the configuration of a network entity according to an embodiment disclosed herein. Refer to Figure 15 , the network entity may include a transceiver 1510, a controller 1520, and a storage unit 1530. The controller 1520 may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0236] The transceiver 1510 may send signals to other network entities / receive signals from other network entities. The controller 1520 may control the overall operation of the UE. The storage unit 1530 may store at least one piece of information sent / received via the transceiver 1510 and information generated via the controller 1520.

[0237] Various embodiments of the present disclosure may be implemented by software including instructions stored in a machine-readable storage medium readable by a machine (e.g., a computer). The machine may be a device that calls instructions from the machine-readable storage medium and operates according to the called instructions, and may include an electronic device. When the instructions are executed by a processor, the processor may directly or using other components execute functions corresponding to the instructions under the control of the processor. The instructions may include code generated or executed by a compiler or an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory" as used herein is a limitation of the medium itself (i.e., tangible, not a signal), rather than a limitation on the persistence of data storage.

[0238] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

[0239] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

[0240] Those skilled in the art will understand that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. In addition, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure generally described herein and shown in the figures may be arranged, substituted, combined, separated, and designed in various different configurations, all of which are contemplated herein.

[0241] Those skilled in the art will understand that the various illustrative logical blocks, modules, circuits, and steps described in this application can be implemented as hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functional sets. Whether such a functional set is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. Skilled artisans may implement the described functional sets in different ways for each particular application, but such design decisions should not be construed as causing a departure from the scope of this application.

[0242] The various illustrative logical blocks, modules, and circuits described in this application can be implemented or executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0243] The steps of the methods or algorithms described in this application can be embodied directly in hardware, in a software module executed by a processor, or in a combination thereof. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read from, and write to, the storage medium. In the alternative, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0244] In one or more exemplary designs, these functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The computer-readable medium includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0245] The above description is only an exemplary embodiment of the present disclosure and is not intended to limit the protection scope of the present disclosure. The protection scope of the present disclosure is determined by the appended claims.

[0246] Although the present disclosure has been described with various embodiments, various changes and modifications can be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Identifying whether the UE is registered for access service in a Standalone Non-Public Network (SNPN) that does not support emergency services; In the case where the UE is registered for access service in the SNPN, identifying whether the dialed number is an emergency number; And In the case where the dialed number is an emergency number, performing an emergency procedure.

2. The method according to claim 1, further comprising: Performing a local deregistration based on determining that the dialed number is an emergency number.

3. The method according to claim 1, wherein performing the emergency procedure comprises: Performing a cell reselection to a cell that supports emergency voice calls.

4. The method according to claim 1, wherein performing the emergency procedure comprises: Selecting a domain for an emergency session; And Based on the selected domain, attempting to initiate an emergency session.

5. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Identifying whether the UE is in an automatic selection mode; In the case where the UE is in the automatic selection mode, determining the coverage of a subscribed Standalone Non-Public Network (SNPN); And Based on the determined coverage of the subscribed SNPN, registering to the subscribed SNPN.

6. The method according to claim 5, further comprising: Powering on the UE; Or Starting to operate in the SNPN access operation mode.

7. The method according to claim 5, Among them, The UE follows the recovery from lack of coverage.

8. The method according to claim 5, Among them, After determining the coverage of the subscribed SNPN, the UE does not return to the registered SNPN or an equivalent SNPN, and Wherein, the subscribed SNPN is used for the selected entry of the subscriber data list.

9. A user equipment (UE) in a wireless communication system, the UE comprising: A transceiver; And A controller configured to: Identify whether the UE is registered for access service in a Standalone Non-Public Network (SNPN) that does not support emergency services, In the case where the UE is registered for access service in the SNPN, identify whether the dialed number is an emergency number, and In the case where the dialed number is an emergency number, perform an emergency procedure.

10. The UE according to claim 9, wherein, The controller is further configured to: Perform a local deregistration based on determining that the dialed number is an emergency number.

11. The UE according to claim 9, wherein, The controller is further configured to: Perform a cell reselection to a cell that supports emergency voice calls.

12. The UE according to claim 9, wherein, The controller is further configured to: Based on the selected domain, attempt to initiate an emergency session.

13. A user equipment (UE) in a wireless communication system, the UE comprising: A transceiver; And A controller configured to: Identify whether the UE is in an automatic selection mode, In the case where the UE is in the automatic selection mode, determine the coverage of a subscribed Standalone Non-Public Network (SNPN), and Based on the determined coverage of the subscribed SNPN, register to the subscribed SNPN.

14. The UE according to claim 13, wherein, The controller is further configured to: Power on the UE; or Start to operate in the SNPN access operation mode; or Follow the recovery from lack of coverage.

15. The UE according to claim 13, Among them, After determining the coverage of the subscribed SNPN, the UE does not return to the registered SNPN or equivalent SNPN, and wherein the subscribed SNPN is used for an entry in the selection of the subscriber data list.

Images