Method and apparatus for selecting SNPN for localized services

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to an embodiment of the disclosure, a method may include adding at least one hosting SNPN to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN and selecting the at least one hosting SNPN for accessing for at least one localized service.

Description

METHOD AND APPARATUS FOR SELECTING SNPN FOR LOCALIZED SERVICES

[0001] The present disclosure is related to wireless communication. More particularly, the present disclosure is related to a method and an apparatus for selecting SNPN for localized services.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz"bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] According to an embodiment of the disclosure, a method performed by a user equipment may include adding at least one hosting stand-alone private network (SNPN) to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, in case that the UE receives a rejection message, from a network, indicating the at least one hosting SNPN is not allowed.

[0009] According to an embodiment of the disclosure, the method may include removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN.

[0010] According to an embodiment of the disclosure, the method may include selecting the at least one hosting SNPN for accessing for at least one localized service.

[0011] According to an embodiment of the disclosure, a user equipment may include a transceiver and a processor coupled with the transceiver.

[0012] According to an embodiment of the disclosure, wherein the processor is configured to add at least one hosting stand-alone private network (SNPN) to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, in case that the UE receives a rejection message, from a network, indicating the at least one hosting SNPN is not allowed.

[0013] According to an embodiment of the disclosure, wherein the processor is configured to remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN.

[0014] According to an embodiment of the disclosure, wherein the processor is configured to select the at least one hosting SNPN for accessing for at least one localized service.

[0015] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0016] Fig. 1 is a sequence diagram that illustrates a scenario in which a UE continues to stay camped in a limited service state in the absence of any suitable hosting SNPNs according to the prior art;

[0017] Fig. 2 is a block diagram that illustrates a schematic of a network apparatus implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein;

[0018] Fig. 3 is a block diagram that illustrates a schematic of the UE implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein;

[0019] Fig. 4 is a sequence diagram that illustrates a scenario in which the UE performs immediate SNPN selection in the hosting SNPN to recover from the limited service state according to the embodiment as disclosed herein;

[0020] Fig. 5 is a flow diagram that illustrates a method for selecting the SNPN for localized services in a limited service state according to the embodiment as disclosed herein; and

[0021] Fig. 6 is a flow diagram that illustrates a method for performing an immediate SNPN selection in a hosting SNPN to recover from the limited service state according to the embodiment as disclosed herein.

[0022] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawing. Further, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimension of some of the elements in the drawing may be exaggerated relative to other elements to help to improve the understanding of aspects of the invention. Furthermore, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to the understanding the embodiments of the invention so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

[0023] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with a plurality of other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

[0024] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically 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, and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in a plurality of semiconductor chips, or on substrate supports such as printed circuit boards, and the like.　The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., a plurality of programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0025] The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

[0026] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0027] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present invention, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made.

[0028] Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. Thus, appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0029] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0030] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0031] The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the examples disclosed herein.

[0032] Throughout the description and claims, the words "comprise", "contain" and "include" and variations thereof, for example "comprising", "containing", and "including" means "including but not limited to", and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, functions, characteristics, and the like.

[0033] Throughout the description and claims, the singular form, for example "a", "an" and "the" encompasses the plural unless the context otherwise requires. For example, reference to "an object" includes reference to one or more of such objects.

[0034] Before undertaking the detailed description below, it may be advantageous to set forth definitions of certain words and phrases used throughout the present disclosure. The term "couple" and the derivatives thereof 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 "transmit", "receive" and "communicate" as well as the derivatives thereof encompass both direct and indirect communication. The terms "include" and "comprise" and the derivatives thereof refer to inclusion without limitation. The term "or"is an inclusive term meaning "and / or". The phrase "associated with" as well as derivatives thereof, refer to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term "controller" refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. 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 and B and C, and any variations thereof. Similarly, the term "set" means one or more. Accordingly, the set of items may be a single item or a collection of two or more items.

[0035] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include computer-executable instructions. The entirety of the one or more computer programs may be stored in a single memory or the one or more computer programs may be divided with different portions stored in different multiple memories.

[0036] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP), a communication processor (CP), a graphical processing unit (GPU), a neural processing unit (NPU), a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0037] As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically 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 and the like, and may optionally be driven by firmware and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block 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 to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0038] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0039] A stand-alone private network (SNPN) is a type of private network that operates independently from public mobile networks. These networks are designed to serve specific organizational needs, offering tailored connectivity solutions within a confined area. The SNPN is deployed with 5G as the core access technology. If a mobile station (MS) supports access to an SNPN for localized services. It maintains a "temporarily forbidden SNPNs for access for localized services in SNPN" and a "permanently forbidden SNPNs for access for localized services in SNPN". If the MS supports access to an SNPN for localized services, then for automatic SNPN selection, the MS cannot select an SNPN which is in either of these lists.

[0040] Furthermore, localized services can be supported by the SNPN. Localized services are those that an SNPN offers in specific geographic regions and for certain amounts of time. A live stream of an ongoing football game or music concert that is exclusively available to spectators within the stadium during those events would be categorized as a localized service. Typically, apps or manual activation are used to grant UEs access to localized services within the SNPN. A UE can only access an SNPN―which offers localized services―while such access is enabled. Permanently deployed SNPNs cannot be accessed by UEs. The home operator configures a list of such SNPN (networks) that offer localized services in the UE using a number of processes so that a UE may recognize, discover, and access such SNPNs. This type of list includes a list of these SNPNs as well as the validity of each one's time and place (e.g., the day's duration and location) when it is available. A UE with localized service enabled searches and camping in those SNPNs, only in those particular regions, and only during those designated hours of the day.

[0041] For example, a UE may only access SNPN-A at location X between 2 p.m. and 3 p.m. on a given day if the validity information of SNPN-A specifies a time validity of 2 p.m. to 3 p.m. The UE adds the SNPN to a forbidden list for SNPN for localized services in SNPN when such an SNPN offering localized service in SNPN rejects a UE with some 5GMM level reject reasons, for example #74 (Temporarily not approved for this SNPN) or #75 (Permanently not authorized for this SNPN). During automated SNPN selection, a UE is unable to choose such an SNPN for localized services.

[0042] Hence, is desirable to address the above mentioned problems and disadvantages or at least provide a useful alternative.

[0043] The principal object of the embodiments herein is to select a SNPN for localized services in a limited service state.

[0044] Yet another object of the embodiments herein is to provide a UE to perform immediate SNPN selection in hosting SNPN to recover from limited service state when either UE implementation specific timer, timer T3245 expires or when the validity information / condition of a hosting SNPN changes from not valid to valid.

[0045] Yet another object of the embodiments herein is to use an SNPN that has been removed from a list of temporarily forbidden SNPNs for access for localized services in SNPN or a list of permanently forbidden SNPNs for access for localized services in SNPN.

[0046] Yet another object of the embodiment herein is to perform an immediate SNPN selection in that SNPN to enable the UE for access to localized services in SNPN, when the access for localized services is available based on the validity information of the SNPN.

[0047] In one aspect, the objectives are achieved by providing a method for selecting a stand-alone non-public network (SNPN) for localized services while in a limited service state. The method includes determining, by a network apparatus, whether an emergency PDU session is not established between a user equipment (UE) and the network apparatus. The UE supports access to an SNPN providing access for localized services in SNPN, the access for localized services in SNPN is enabled and the UE is in the limited service state. Further, the method includes determining, by the network apparatus, whether a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met, when the emergency PDU session is not established between the UE and the network apparatus. The hosting SNPN belongs to a list of temporarily forbidden SNPNs for access for localized services in SNPN or a list of permanently forbidden SNPNs for access for localized services in SNPN. In addition, the method includes removing, by the UE, the hosting SNPN from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN when the timer associated with the hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met. The UE performs an immediate SNPN selection in the hosting SNPN to recover from the limited service state when the hosting SNPN is removed from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN.

[0048] In an embodiment, the method includes determining, by the UE, whether an emergency PDU session is established between the UE and the network apparatus. The UE performs the SNPN selection in the hosting SNPN to recover from the limited service state subsequently after the emergency PDU session is released.

[0049] In an embodiment, the timer is a T3245 timer or a MS implementation specific timer not shorter than 60 minutes.

[0050] In an embodiment, the validity information includes at least one of a time validity information, location validity information, and a location assistance information.

[0051] In one aspect, the objectives are achieved by providing a method for selecting a stand-alone non-public network (SNPN) for localized services while in a limited service state. The method includes detecting, by a user equipment (UE), whether the UE is in a limited service state. Further, the method includes receiving, by the UE, an update from a network apparatus when the UE is in the limited service state. The update indicates that an emergency PDU session is not established between the UE and the network apparatus, and at least one of a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met. In addition, the method includes performing, by the UE, an immediate SNPN selection in the hosting SNPN to recover from the limited service state when the hosting SNPN is removed from a list of temporarily forbidden SNPNs for access for localized services in SNPN or a list of permanently forbidden SNPNs for access for localized services in SNPN.

[0052] In an embodiment, the method includes receiving, by the UE, a second update from the network apparatus when the UE is in the limited service state, wherein the second update indicates that the emergency PDU session is established between the UE and the network apparatus. In addition, the method includes performing, by the UE, the SNPN selection in the hosting SNPN to recover from the limited service state subsequently after the emergency PDU session is released.

[0053] In one aspect, the objectives are achieved by providing a network apparatus for hosting a stand-alone non-public network (SNPN) in a limited service state in a wireless communication system. The network apparatus includes a memory, a processor coupled to the memory, and a SNPN controller communicatively coupled to the processor and the memory. The SNPN controller determines whether an emergency PDU session is not established between a user equipment (UE) and the network apparatus. The UE supports access to an SNPN providing access for localized services in SNPN, an access for localized services in SNPN is enabled and the UE is in the limited service state. Further, the SNPN controller determines whether a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met, when the emergency PDU session is not established between the UE and the network apparatus. The hosting SNPN belongs to a list of temporarily forbidden SNPNs for access for localized services in SNPN or a list of permanently forbidden SNPNs for access for localized services in SNPN. In addition, the SNPN controller removes the hosting SNPN from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN when the timer associated with the hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met. The UE performs an immediate SNPN selection in the hosting SNPN to recover from the limited service state when the hosting SNPN is removed from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN.

[0054] In an embodiment, the SNPN controller determines whether an emergency PDU session is established between the UE and the network apparatus. The UE performs the SNPN selection in the hosting SNPN to recover from the limited service state subsequently after the emergency PDU session is released.

[0055] In an embodiment, the timer is a T3245 timer or a MS implementation specific timer not shorter than 60 minutes.

[0056] In an embodiment, the validity information includes at least one of a time validity information, location validity information, and a location assistance information.

[0057] In one aspect, the objectives are achieved by providing a user equipment (UE) for selecting a stand-alone non-public network (SNPN) for localized services while in a limited service state. The UE includes a memory, a processor coupled to the memory, and a UE controller communicatively coupled to the memory and the processor. The UE controller detects whether the UE is in a limited service state. Further, the UE controller receives an update from a network apparatus when the UE is in the limited service state. The update indicates that an emergency PDU session is not established between the UE and the network apparatus, and at least one of a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met. In addition, the UE controller performs an immediate SNPN selection in the hosting SNPN to recover from the limited service state when the hosting SNPN is removed from a list of temporarily forbidden SNPNs for access for localized services in SNPN or a list of permanently forbidden SNPNs for access for localized services in SNPN.

[0058] In an embodiment, the UE controller receives a second update from the network apparatus when the UE is in the limited service state. The second update indicates that the emergency PDU session is established between the UE and the network apparatus. In addition, the UE controller performs the SNPN selection in the hosting SNPN to recover from the limited service state subsequently after the emergency PDU session is released.

[0059] 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. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

[0060] Fig. 1 is a sequence diagram that illustrates a scenario in which a UE (102) continues to stay camped in a limited service state in the absence of any suitable hosting SNPNs according to the prior art. As shown in the sequence diagram, the UE (102) is in communication with a network apparatus (104).

[0061] At step S1, the UE (102) is registered in SNPN-A. At step S2, the UE (102) supports access for localized services in the SNPN and the access for localized services in the SNPN is enabled. At step S3, the UE (102) is configured with a non-empty CH_list_SNPNs or CH_list_GINs. At step S4, the UE (102) moves to an SNPN (for example, SNPN-B, which is also a hosting SNPN) configuredin the CH_list_SNPNs or broadcasting GIN(s) configured in CH_list_GINs. At step S5, the UE (102) tries to register in SNPN-B by sending a registration request message to the network apparatus (104).

[0062] At step S6, the network apparatus (104) rejects the registration request received with a cause Reject_cause. For instance, the rejection request may be rejected because the SNPN-B is configured with a validity information, and the UE (102) is trying to access this SNPN while the validity information is not met. At step S7, the UE (102) adds the SNPN-B to the Forbidden_SNPN_list. At step S8, the UE (102) starts the implementation specific timer or timer T3245. At step S9, the UE (102) does not find any suitable SNPN configured in the CH_list_SNPNs or any SNPN that broadcasts GIN(s) configured in the CH_list_GINs for the UE (102) to select and access for localized services. At step S10, an event of either the implementation specific timer expires / timer T3245 expires or the validity information of the SNPN changes from not valid to valid. The UE (102) shall be in the limited service state in the absence of any suitable hosting SNPNs. The UE (102) will stay camped in the SNPN-B and remain in limited service state. The disadvantage of the above conventional method also exists for equivalent hosting SNPNs as well. For example, if the UE implementation specific timer expires / T3245 expires, or the time validity of the SNPN changes from not met to met (for example, current time is 2 pm of the day, and the validity time for SNPN-B is from 2 pm to 4 pm), the UE (102) will remove the SNPN from the Forbidden_SNPN_list. However, as per the current art, the UE (102) will not use this information, and continue to stay camped for limited services in SNPN-B.

[0063] In general a mobile station (MS) operating in SNPN access operation mode over 3rdGeneration Partnership Project (3GPP) access shall perform the SNPN selection process. In an example, the MS may be another term for the UE (102). When the MS supports access to an SNPN providing access for localized services in the SNPN, the MS shall maintain the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN" per entry of the "list of subscriber data" and per the Public Land Mobile Network (PLMN) subscription. The MS shall use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. The MS shall add the SNPN to the list of "temporarily forbidden SNPNs" for access for localized services in the SNPN, when the SNPN was selected according to the SNPN selection criterion for localized services as mentioned in 3GPP TS 23.122 and for onboarding services, when the MS is registered for onboarding services in the SNPN or performing initial registration for onboarding services in the SNPN.

[0064] The MS shall add the SNPN to the list of "temporarily forbidden SNPNs", when the MS supports access to the SNPN using credentials from a credentials holder, equivalent SNPNs or both associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, when a message with cause value #74 "Temporarily not authorized for this SNPN" (see 3GPP TS 24.501

[0064] ) is received by the MS in response to an LR request from the SNPN. When the message is integrity-protected or the message is not integrity-protected and the value of the SNPN-specific attempt counter for that SNPN is equal to the MS implementation specific maximum value as defined in 3GPP TS 24.501

[0064] , then the MS shall start an MS implementation specific timer not shorter than 60 minutes.

[0065] 3GPP has introduced the concept of localized services. Localized service is a service which is localized (i.e. provided at specific / limited area) and / or can be bounded in time. The service can be realized via applications (e.g. live or on-demand audio / video stream, electric game, IP Multimedia Subsystem (IMS), etc.), or connectivity (e.g. User Equipment (UE) to UE, UE to Data Network, etc.). A service provider that provides such service is called a localized service provider. A localized service provider is an application provider or network operator who make their services localized and to be offered to an end user via a hosting network.

[0066] When the MS supports access to the SNPN providing access for localized services in the SNPN, the SNPN selection parameters for access for localized services in the SNPN, consisting of:

[0067] - A "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in the SNPN", where each entry contains an SNPN identity and a validity information consisting of time validity information; and

[0068] - A "credentials holder controlled prioritized list of preferred Group Identity for Network Selection (GINs) for access for localized services in the SNPN", where each entry contains an GIN and a validity information consisting of time validity information.

[0069] Provisioning information for the SNPN selection (when the access for localized services in the SNPN has been enabled) by an MS supporting access to an SNPN providing access for localized services in the SNPN consisting of: - a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in the SNPN", where each entry contains an SNPN identity and a validity information consisting of time validity information;

[0070] - a "credentials holder controlled prioritized list of preferred GINs for access for localized services in the SNPN", where each entry contains a GIN and a validity information consisting of time validity information; or

[0071] - Both of the above.

[0072] Validity condition / information consists of:

[0073] - Time validity information, i.e. time periods (defined by start and end times) when access to the SNPN for accessing localized services is allowed; and / or

[0074] - Location assistance validity information consisting of:

[0075] - Geolocation information, and / or,

[0076] Tracking area information of serving networks, i.e. lists of Tracking Area Code (TACs) per PLMN ID or per PLMN ID and NID.

[0077] 5GS forbidden tracking areas for roaming or 5GS forbidden tracking areas for regional provision of service is a list of forbidden tracking areas where the UE (102) is not allowed to operate for normal services (apart from emergency). The MS adds a TA to this list when the MS receives reject causes #12, #15 or #13 for example. When the UE (102) is not operating in the SNPN access operation mode, the UE (102) shall store a list of "5GS forbidden tracking areas for roaming", as well as a list of "5GS forbidden tracking areas for regional provision of service". Otherwise, the UE (102) shall store a list of "5GS forbidden tracking areas for roaming":

[0078] -Per SNPN; and

[0079] -When the UE (102) supports access to the SNPN using credentials from the credentials holder, equivalent SNPNs or both, per entry of the "list of subscriber data" or, when the UE (102) supports access to the SNPN using credentials from the credentials holder, PLMN subscription; and store a list of "5GS forbidden tracking areas for regional provision of service":

[0080] - Per SNPN; and

[0081] -When the UE (102) supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, per entry of the "list of subscriber data" or, when the UE (102) supports access to an SNPN using credentials from a credentials holder, PLMN subscription.

[0082] The term 5GMM sublayer state in this embodiment is at least one of the below:

[0083] 1) 5GMM-NULL

[0084] 2) 5GMM-DEREGISTERED

[0085] a) 5GMM-DEREGISTERED.NORMAL-SERVICE

[0086] b) 5GMM-DEREGISTERED.LIMITED-SERVICE

[0087] c)5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION

[0088] d) 5GMM-DEREGISTERED.PLMN-SEARCH

[0089] e) 5GMM-DEREGISTERED.NO-SUPI

[0090] f) 5GMM-DEREGISTERED.NO-CELL-AVAILABLE

[0091] g) 5GMM-DEREGISTERED.eCALL-INACTIVE

[0092] h) 5GMM-DEREGISTERED.INITIAL-REGISTRATION-NEEDED

[0093] 3) 5GMM-REGISTERED-INITIATED

[0094] 4) 5GMM-REGISTERED

[0095] a) 5GMM-REGISTERED.NORMAL-SERVICE

[0096] b) 5GMM-REGISTERED.NON-ALLOWED-SERVICE

[0097] c)5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE

[0098] d) 5GMM-REGISTERED.LIMITED-SERVICE

[0099] e) 5GMM-REGISTERED.PLMN-SEARCH

[0100] f) 5GMM-REGISTERED.NO-CELL-AVAILABLE

[0101] g) 5GMM-REGISTERED.UPDATE-NEEDED

[0102] 5) 5GMM-DEREGISTERED-INITIATED

[0103] 6) 5GMM-SERVICE-REQUEST-INITIATED

[0104] Forbidden_SNPN_list: In this embodiment this will refer to "temporarily forbidden SNPNs for access for localized services in SNPN" & "permanently forbidden SNPNs for access for localized services in SNPN" or all of them.

[0105] Reject_cause:In this embodiment this will refer to #74 or #74 or other existing 5GMM causes as well, or new 5GMM cause like #XX

[0106] (Localized service not available) which can lead to the UE (102) adding an SNPN to Forbidden_SNPN_list.

[0107] CH_list_GINs:In this embodiment, this will refer to "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN".

[0108] CH_list_SNPNs:In this embodiment this will refer to "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN".

[0109] Event_A:In this embodiment this event can be either of UE implementation specific timer expiry, expiry of timer T3245 or if the validity information / condition of an SNPN changes from not valid to valid.

[0110] The term "limited service state" in this embodiment is used to indicate 5GMM-DEREGISTERED.LIMITED-SERVICE state or 5GMM-REGISTERED.LIMITED-SERVICE state and interchangeably and have same meaning.

[0111] The term "hosting SNPN" in this embodiment refers to an SNPN that is configured in CH_list_SNPNs or that broadcasts GIN(s) configured in CH_list_GINs.

[0112] In the current art, when an event of either the implementation specific timer expires / timer T3245 expires or the validity information of the SNPN changes from not valid to valid, the UE (102) will be in the limited service state in the absence of any suitable hosting SNPNs. Access for localized services will be impacted, and the SNPN will not be able to gain access for localized services. For instance, if the implementation specific timer expires / T3245 expires, or the time validity of the hosting SNPN changes from not met to met, the UE (102) will remove the hosting SNPN from the Forbidden_SNPN_list. However, as per the current art, the UE (102) will not use this information, and continue to stay camped for limited services in the hosting SNPN.

[0113] In the proposed solution, it is checked whether an emergency PDU session is established between the UE (102) and the network apparatus (104). If there is no emergency PDU session established, then the network apparatus (104) determined whether the timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met. Based on this determination, the hosting SNPN is removed from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN. Thus, the proposed solution is capable of using the SNPN (hosting SNPNS) being removed from the forbidden SNPN list for localized services, and perform an immediate SNPN selection to enable the user access to local services in SNPN.

[0114] Referring now to the drawings, and more particularly to Figs. 2 through 6 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0115] Fig. 2 is a block diagram that illustrates a schematic of the network apparatus (104) implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein. As shown, the network apparatus (104) includes a processor (202), a memory (204), an I / O interface (206), and a SNPN controller (208).

[0116] The processor (202) communicates with the memory (204), the I / O interface (206) and the SNPN controller (208). The processor (202) is configured to execute instructions stored in the memory (204) and to perform various processes. The processor (202) may include one or a plurality of processors, may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0117] The SNPN controller (208) may be a part of the processor (202). The SNPN controller (208) may be operated as a part of the processor (202).

[0118] The memory (204) includes storage locations to be addressable through the processor (202). The memory (204) is not limited to a volatile memory and / or a non-volatile memory. Further, the memory (204) may include a plurality of computer-readable storage media. The memory (204) may include non-volatile storage elements. For example, non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0119] The I / O interface (206) transmits the information between the memory (204) and external peripheral devices. The peripheral devices are the input-output devices associated with the UE (102). Further, the SNPN controller (208) communicates with the I / O interface (206) and the memory (204). The SNPN controller (208) may be communicatively coupled to the memory (204) and the processor (202). The SNPN controller (208) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0120] In an embodiment, the SNPN controller (208) determines whether an emergency packet data unit (PDU) session is not established between the UE (102) and the network apparatus (104). Emergency PDU sessions refer to a specific type of data session in wireless networks, designed to ensure that emergency services can access necessary data and communication channels, even in situations where the network is congested or certain restrictions are in place. Emergency PDU sessions may use dedicated network pathways or bearers, which are specially configured to handle emergency data traffic. Further, the UE (102) supports access to an SNPN providing access for localized services in SNPN, and an access for localized services in SNPN is enabled and the UE (102) is in the limited service state. For instance, the limited service state may refer to a condition where the UE (102) has only restricted access to network services. In this state, the UE (102) may still perform certain essential functions, but does not have full access to the network for regular communication and data services.

[0121] In an embodiment, the SNPN controller (208) determines whether a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met, when the emergency PDU session is not established between the UE (102) and the network apparatus (104). For instance, the timer is a T3245 timer or a MS implementation specific timer not shorter than 60 minutes. For instance, the T3245 timer is a network timer and may be associated with the NAS (Non-Access Stratum) layer of the UE (102). The T3245 timer handles signaling between the UE (102) and the network apparatus (104). The T3245 timer plays an important role in maintaining the security integrity of the communication between the UE (102) and the network apparatus (104).

[0122] In an embodiment, the hosting SNPN belongs to a list of temporarily forbidden SNPNs for access for localized services in SNPN or a list of permanently forbidden SNPNs for access for localized services in SNPN. The forbidden SNPNs includes identifiers of SNPNs that the UE (102) should avoid. These identifiers are usually based on the SNPN Identifier (SNPN-ID), which uniquely identifies each non-public network. The main purpose of maintaining a list of forbidden SNPNs is to prevent the UE (102) from attempting to connect to certain non-public networks that may be restricted, either due to security policies, subscription issues, or administrative decisions. The list of temporarily forbidden SNPNs includes specific SNPNs to which the UE (102) should not attempt to connect for a temporary period. The list of permanently forbidden SNPNs includes specific SNPNs to which the UE (102) is permanently restricted from attempting to connect. By managing the list of forbidden SNPNs, both the UE (102) and the network apparatus (104) can ensure that connections are only made to authorized and safe non-public networks.

[0123] In an embodiment, the SNPN controller (208) removes the hosting SNPN from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN. The hosting SNPN is removed from the respective lists when the timer associated with the hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met. For example, if the timer exceeds 60 minutes, then the hosting SNPN may be removed.

[0124] In an embodiment, the UE (102) performs an immediate SNPN selection in the hosting SNPN to recover from the limited service state when the hosting SNPN is removed from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN.

[0125] In an embodiment, the SNPN controller (208) determines whether the emergency PDU session is established between the UE (102) and the network apparatus (104). The UE (102) performs the SNPN selection in the hosting SNPN to recover from the limited service state subsequently after the emergency PDU session is released.

[0126] Fig. 3 is a block diagram that illustrates a schematic of the UE (102) implemented to carry out the disclosed subject matter according to the embodiment as disclosed herein. As shown, the UE (102) includes the processor (302), the memory (304), the I / O interface (306), and a UE controller (310). The UE (102) may include, but not limited to a smartphone, personal computer (PC), tablet, and the like.

[0127] The UE controller (310) communicates with the I / O interface (306) and the memory (304). The UE controller (310) may be communicatively coupled to the memory (304) and the processor (302). The UE controller (310) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0128] The UE controller (310) may be a part of the processor (302). The UE controller (310) may be operated as a part of the processor (302).

[0129] In an embodiment, the UE controller (310) detects whether the UE (102) is in a limited service state. The UE (102) may only have restricted access to network services in the limited service state. The UE (102) may still carry out some basic operations in this mode, but it is not fully connected to the network for regular data services and communication.

[0130] In an embodiment, the UE controller (310) receives an update from the network apparatus (104) when the UE (102) is in the limited service state. The update indicates that an emergency PDU session is not established between the UE (102) and the network apparatus (104). The update may also provide an indication that a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met.

[0131] In an embodiment, the UE controller (310) performs an immediate SNPN selection in the hosting SNPN to recover from the limited service state. The immediate SNPN selection is performed when the hosting SNPN is removed from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN. The hosting SNPN may be removed from the respective lists when the timer expires or a validity information changes from not met to met.

[0132] In an embodiment, the UE controller (310) receives a second update from the network apparatus (104) when the UE (102) is in the limited service state. The second update indicates that the emergency PDU session is established between the UE (102) and the network apparatus (104). In this case, the UE controller (310) performs the SNPN selection in the hosting SNPN to recover from the limited service state subsequently after the emergency PDU session is released.

[0133] Fig. 4 is a sequence diagram that illustrates a scenario in which the UE (102) performs immediate SNPN selection in the hosting SNPN to recover from the limited service state according to the embodiment as disclosed herein. As shown in the sequence diagram, the UE (102) is in communication with the network apparatus (104).

[0134] At step S1, the UE (102) is registered in SNPN-A. At step S2, the UE (102) supports access for localized services in the SNPN and the access for localized services in the SNPN is enabled. At step S3, the UE (102) is configured with a non-empty CH_list_SNPNs or CH_list_GINs. At step S4, the UE (102) moves to an SNPN (for example, SNPN-B), which is also a hosting SNPN, configuredin CH_list_SNPNs or broadcasting GIN(s) configured in CH_list_GINs. At step S5, the UE (102) tries to register in SNPN-B by sending a registration request message to the network apparatus (104).

[0135] At step S6, the network apparatus (104) rejects the registration request received by the UE (102) with cause Reject_cause. The network apparatus (104) may reject the request because the SNPN-B is configured with a validity information, and the UE (102) is trying to access this SNPN while validity information is not met. At step S7, the UE (102) adds SNPN-B to the Forbidden_SNPN_list. At step S8, the UE (102) starts the implementation specific timer or timer T3245. At step S9, the UE (102) does not find any suitable SNPN configured in CH_list_SNPNs or any SNPN that broadcasts GIN(s) configured in CH_list_GINs for the UE (102) to select and access for localized services. At step S10, an event (for example, event A) of the implementation specific timer / timer T3245 expires or the validity information of the SNPN changes from not valid to valid. At step S11, the UE (102) performs an immediate SNPN selection in the SNPN-B to recover from the limited service state when the implementation specific timer / timer T3245 expires or when the validity information of an SNPN changes from not valid to valid.

[0136] In an example, the UE (102) supports access to an SNPN providing localized services, and the access for localized services has been enabled. The UE (102) tries to access the hosting SNPN (for example, SNPN-B). The UE (102) receives a Reject_cause from the network apparatus (104) leading to the UE (102) adding SNPN-B to a Forbidden_SNPN_list. The UE (102) will either start the implementation specific timer or timer T3245. After this, the UE (102) does not find any suitable SNPN which is configured in CH_list_SNPNs or any SNPN that broadcasts GIN(s) configured in CH_list_GINs for access to localized services. Now, if the implementation specific timer / timer T3245 expires or the time validity of the SNPN changes from not met to met (for example, the current time is 2 pm, and the validity time for SNPN-B is from 2 pm to 4 pm), the UE (102) will remove the SNPN from the Forbidden _SNPN_list. As a solution, the UE (102) should immediately start performing SNPN selection in SNPN-B to recover from limited service.

[0137] Fig. 5 is a flow diagram that illustrates a method for selecting the SNPN for localized services in a limited service state according to the embodiment as disclosed herein. The method includes steps (502-506). Each step is explained in further detail below.

[0138] At step (502), the SNPN controller (208) determines whether an emergency PDU session is not established between the UE (102) and the network apparatus (104). Emergency PDU sessions are a particular kind of data session in wireless networks that are intended to guarantee that emergency services may access the data and communication channels they require, even when there are network congestion or limits in place. Bearers or dedicated network channels that are specifically set up to manage emergency data traffic may be used for emergency PDU sessions. Additionally, the UE (102) is in the restricted service state and supports access to an SNPN that grants access to localized services in SNPN. Additionally, the UE (102) has enabled access to localized services in SNPN. The UE (102) may only have restricted access to network services, for example, in the limited service state. In this state, the UE (102) may still perform certain essential functions, but does not have full access to the network for regular communication and data services.

[0139] At step (504), it is determined whether a timer associated with a hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met, when the emergency PDU session is not established between the UE (102) and the network apparatus (104). For instance, the timer is a T3245 timer or a MS implementation specific timer not shorter than 60 minutes. For instance, the T3245 timer is a network timer and may be associated with the NAS (Non-Access Stratum) layer of the UE (102). Signalling between the UE (102) and the network apparatus　(104), is handled by the T3245 timer. The T3245 timer is crucial to preserving the communication's security integrity between the network apparatus (104), which is connected to the UE (102).

[0140] At step (506), the hosting SNPN is removed from the hosting SNPN from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN. When a hosting SNPN's validity information changes from not met to met, or when the timer associated with the hosting SNPN has expired, the hosting SNPN is removed from the corresponding lists. For instance, the hosting SNPN may be deleted if the timer goes over 60 minutes.

[0141] FIG. 6 is a flow diagram that illustrates a method for handling the UE (102) during the unavailability period through the registration procedure according to an embodiment as disclosed herein. The method includes steps (602-610). Each step is explained in further detail below.

[0142] At step (602), it is detected whether the UE (102) is in the limited service state. In the limited service state, the UE (102) may still perform certain essential functions, but does not have full access to the network for regular communication and data services.

[0143] At step (604), an update is received from the network apparatus (104) when the UE (102) is in the limited service state. For instance, the update indicates that an emergency PDU session is not established between the UE (102) and the network apparatus (104), and the timer associated with the hosting SNPN has expired or a validity information of the hosting SNPN changes from not met to met.

[0144] At step (606), the UE (102) performs an immediate SNPN selection in the hosting SNPN to recover from the limited service state. The immediate SNPN selection is performed when the hosting SNPN is removed from the list of temporarily forbidden SNPNs for access for localized services in SNPN or the list of permanently forbidden SNPNs for access for localized services in SNPN. The hosting SNPN may be removed from the respective lists when the timer expires or a validity information changes from not met to met.

[0145] According to an embodiment of the disclosure, a method performed by a user equipment may include adding at least one hosting stand-alone private network (SNPN) to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, in case that the UE receives a rejection message, from a network, indicating the at least one hosting SNPN is not allowed.

[0146] According to an embodiment of the disclosure, the method may include removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN.

[0147] According to an embodiment of the disclosure, the method may include selecting the at least one hosting SNPN for accessing for at least one localized service.

[0148] According to an embodiment of the disclosure, the method may include identifying whether an emergency protocol data unit (PDU) session is established.

[0149] According to an embodiment of the disclosure, the method may include in case that the emergency PDU session is not established, selecting the at least one hosting SNPN for accessing for at least one localized service.

[0150] According to an embodiment of the disclosure, the method may include in case that an emergency PDU session is established, selecting the at least one hosting SNPN for accessing for at least one localized service after the emergency PDU session is released.

[0151] According to an embodiment of the disclosure, wherein the validity information includes at least one of a time validity information or location validity information.

[0152] According to an embodiment of the disclosure, the method may include removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one time period matches current time of the UE.

[0153] According to an embodiment of the disclosure, wherein the at least time period is included in the time validity information.

[0154] According to an embodiment of the disclosure, the method may include removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one location information matches current location of the UE.

[0155] According to an embodiment of the disclosure, wherein the at least one location information is included in the location validity information.

[0156] According to an embodiment of the disclosure, the method may include starting the timer in case that adding at least one hosting SNPN to a list of at least one temporarily forbidden SNPN, or a list of at least one permanently forbidden SNPN.

[0157] According to an embodiment of the disclosure, wherein an expiration value of the timer is determined based on the validity information.

[0158] According to an embodiment of the disclosure, the method may include starting the timer in case that the rejection message is integrity protected, or in case that the rejection message is not integrity protected and a value of SNPN connection attempt counter for the at least one hosting SNPN is equal to a threshold.

[0159] According to an embodiment of the disclosure, wherein the threshold is not greater than 10.

[0160] According to an embodiment of the disclosure, wherein an expiration value of the timer is not shorter than 60 minutes.

[0161] According to an embodiment of the disclosure, a user equipment may include a transceiver and a processor coupled with the transceiver.

[0162] According to an embodiment of the disclosure, wherein the processor is configured to add at least one hosting stand-alone private network (SNPN) to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, in case that the UE receives a rejection message, from a network, indicating the at least one hosting SNPN is not allowed.

[0163] According to an embodiment of the disclosure, wherein the processor is configured to remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN.

[0164] According to an embodiment of the disclosure, wherein the processor is configured to select the at least one hosting SNPN for accessing for at least one localized service.

[0165] According to an embodiment of the disclosure, wherein the processor is configured to identify whether an emergency protocol data unit (PDU) session is established.

[0166] According to an embodiment of the disclosure, wherein the processor is configured to in case that the emergency PDU session is not established, select the at least one hosting SNPN for accessing for at least one localized service.

[0167] According to an embodiment of the disclosure, wherein the processor is configured to in case that an emergency PDU session is established, select the at least one hosting SNPN for accessing for at least one localized service after the emergency PDU session is released.

[0168] According to an embodiment of the disclosure, wherein the validity information includes at least one of a time validity information or location validity information.

[0169] According to an embodiment of the disclosure, wherein the processor is configured to remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one time period matches current time of the UE.

[0170] According to an embodiment of the disclosure, wherein the at least time period is included in the time validity information.

[0171] According to an embodiment of the disclosure, wherein the processor is configured to remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one location information matches current location of the UE.

[0172] According to an embodiment of the disclosure, wherein the at least one location information is included in the location validity information.

[0173] According to an embodiment of the disclosure, wherein the processor is configured to start the timer in case that the rejection message is integrity protected, or in case that the rejection message is not integrity protected and a value of SNPN connection attempt counter for the at least one hosting SNPN is equal to a threshold.

[0174] According to an embodiment of the disclosure, wherein the threshold is not greater than 10.

[0175] According to an embodiment of the disclosure, wherein the processor is configured to wherein an expiration value of the timer is not shorter than 60 minutes.

[0176] The various actions, acts, blocks, steps, or the like in the method is performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like are omitted, added, modified, skipped, or the like without departing from the scope of the proposed method.

[0177] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a user equipment (UE), comprising:adding at least one hosting stand-alone private network (SNPN) to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, in case that the UE receives a rejection message, from a network, indicating the at least one hosting SNPN is not allowed;removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN; andselecting the at least one hosting SNPN for accessing for at least one localized service.2.The method of claim 1, wherein the selecting the at least one hosting SNPN for accessing for at least one localized service comprising:identifying whether an emergency protocol data unit (PDU) session is established; andin case that the emergency PDU session is not established, selecting the at least one hosting SNPN for accessing for at least one localized service.3.The method of claim 2, comprising:in case that an emergency PDU session is established, selecting the at least one hosting SNPN for accessing for at least one localized service after the emergency PDU session is released.4.The method of claim 1,wherein the validity information includes at least one of a time validity information or location validity information.5.The method of claim 1, wherein the removing the at least one hosting SNPN comprising:removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one time period matches current time of the UE,wherein the at least time period is included in the time validity information.6.The method of claim 5, wherein the removing the at least one hosting SNPN comprising:removing the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one location information matches current location of the UE,wherein the at least one location information is included in the location validity information.7.The method of claim 1, further comprising:starting the timer in case that adding at least one hosting SNPN to a list of at least one temporarily forbidden SNPN, or a list of at least one permanently forbidden SNPN,wherein an expiration value of the timer is determined based on the validity information.8.The method of claim 1, further comprisingstarting the timer in case that the rejection message is integrity protected, or in case that the rejection message is not integrity protected and a value of SNPN connection attempt counter for the at least one hosting SNPN is equal to a threshold,wherein the threshold is not greater than 10, andwherein an expiration value of the timer is not shorter than 60 minutes.9.A user equipment (UE), comprising:a transceiver; anda processor coupled with the transceiver, and configured to:add at least one hosting stand-alone private network (SNPN) to a list of at least one temporarily forbidden SNPN for access for at least one localized service in SNPN, or a list of at least one permanently forbidden SNPN for access for at least one localized service in SNPN, in case that the UE receives a rejection message, from a network, indicating the at least one hosting SNPN is not allowed;remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, based on an expiration of a timer or validity information of the at least one hosting SNPN; andselect the at least one hosting SNPN for accessing for at least one localized service.10.The UE of claim 9, wherein the processor is further configured to:identify whether an emergency protocol data unit (PDU) session is established; andin case that the emergency PDU session is not established, select the at least one hosting SNPN for accessing for at least one localized service.11.The UE of claim 9, wherein the processor is further configured to:in case that an emergency PDU session is established, select the at least one hosting SNPN for accessing for at least one localized service after the emergency PDU session is released.12.The UE of claim 9, wherein the validity information includes at least one of a time validity information or location validity information.13.The UE of claim 9, wherein the processor is further configured to:remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one time period matches current time of the UE,wherein the at least time period is included in the time validity information.14.The UE of claim 13, wherein the processor is further configured to:remove the at least one hosting SNPN from the list of the at least one temporarily forbidden SNPN, or the list of the at least one permanently forbidden SNPN, in case that at least one location information matches current location of the UE,wherein the at least one location information is included in the location validity information.15.The UE of claim 9, wherein the processor is further configured to:start the timer in case that the rejection message is integrity protected, or in case that the rejection message is not integrity protected and a value of SNPN connection attempt counter for the at least one hosting SNPN is equal to a threshold,wherein the threshold is not greater than 10, andwherein an expiration value of the timer is not shorter than 60 minutes.

Images