Method and apparatus for deleting snpn from forbidden snpn list

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 performed by a user equipment may include in case that the UE supports access to at least one stand alone non-public network(SNPN), storing at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list, receiving, from a network, a steering of roaming(SOR) information, and in case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), deleting SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.

Description

METHOD AND APPARATUS FOR DELETING SNPN FROM FORBIDDEN SNPN LIST

[0001] The present disclosure relates to a wireless communication, and more specifically related to a method and an apparatus for deleting a Stand-alone non-Public Network (SNPN) from a forbidden SNPN list based on a Group ID for Network Selection (GIN).

[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(UE) may include in case that the UE supports access to at least one stand alone non-public network(SNPN), storing at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list.

[0009] According to an embodiment of the disclosure, the method may include receiving, from a network, a steering of roaming(SOR) information.

[0010] According to an embodiment of the disclosure, the method may include in case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), deleting SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.

[0011] According to an embodiment of the disclosure, a method performed by a network entity may include transmitting, to a user equipment(UE), a reject message.

[0012] According to an embodiment of the disclosure, wherein the reject message is used, at the UE, to store the at least one stand alone non-public network(SNPN) identifier ID and the at least one broadcasted group ID for network selection (GIN) to the forbidden SNPN list.

[0013] According to an embodiment of the disclosure, the method may include transmitting, to the UE, a steering of roaming(SOR) information.

[0014] According to an embodiment of the disclosure, wherein the SOR information is used, at the UE, to delete the at least one SNPN ID from the forbidden SNPN list based on the at least one broadcasted GIN, and at least one of SOR-SNPN-selection information(SOR-SNPN-SI) or SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS) in case that the SOR information includes the at least one of SOR-SNPN-SI or SOR-SNPN-SI-LS.

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

[0016] According to an embodiment of the disclosure, wherein the processor is further configured to in case that the UE supports access to at least one stand alone non-public network(SNPN), store at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list.

[0017] According to an embodiment of the disclosure, wherein the processor is further configured to receive, from a network, a steering of roaming(SOR) information.

[0018] According to an embodiment of the disclosure, wherein the processor is further configured to in case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), delete SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.

[0019] According to an embodiment of the disclosure, a network entity may include may include a transceiver and a processor coupled with the transceiver.

[0020] According to an embodiment of the disclosure, wherein the processor is further configured to transmit, to a user equipment(UE), a reject message.

[0021] According to an embodiment of the disclosure, wherein the processor is further configured to transmit, to the UE, a steering of roaming(SOR) information.

[0022] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings.

[0023] FIG. 1 is a flow chart that illustrate the inadequacy of prior art in enabling a UE to delete the first SNPN with reference to a first GIN entry in a CH controlled prioritized list of GINs.

[0024] FIG. 2 is a flow chart that illustrates to operations undertaken by the UE to eliminate the first SNPN from a prohibited SNPN list, following the receipt of a first GIN entity in a wireless network, according to the embodiments as disclosed herein.

[0025] FIG. 3 is a flow chart that illustrates technical operations performed by the UE to remove the first SNPN from the forbidden SNPN list that were attempted due to a broadcasted GIN matching entry in CH list GINs earlier in the wireless network, according to the embodiments as disclosed herein.

[0026] FIG. 4 is a flow chart illustrating technical operations performed by the UE to remove all the entries from the forbidden SNPN list in the wireless network, according to the embodiments as disclosed herein.

[0027] FIG. 5 is a flow chart illustrating technical operations performed by the UE to remove all the entries from the forbidden SNPN list, with empty CH list GINs but the non-empty CH list SNPNs in the wireless network, according to the embodiments as disclosed herein.

[0028] FIG. 6 is a flow chart illustrating technical operations performed by the UE to remove combination a first SNPN and a first GIN from the Forbidden SNPN list in the wireless network, according to the embodiments as disclosed herein.

[0029] FIG. 7 illustrates various hardware components of the UE, according to the embodiments as disclosed herein.

[0030] FIG. 8 is a flow chart that illustrates a method for deleting a SNPN from a forbidden SNPN list in the wireless network, according to the embodiments as disclosed herein.

[0031] FIG. 9 shows various hardware components of the network apparatus, according to the embodiments as disclosed herein.

[0032] FIG. 10 is a flow chart illustrating a method, implemented by the network apparatus, for deleting the SNPN from the forbidden SNPN list in the wireless network, according to the embodiments as disclosed herein.

[0033] 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 one or more 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.

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

[0035] 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. The terms "comprise", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

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

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

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

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

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

[0041] Generally, if a Mobile Station (MS) supports access to a Stand-alone non-Public Network (SNPN) providing access for localized services in the SNPN, the MS maintains one list of a "temporarily forbidden SNPNs for access for localized services in SNPN" and one list of a "permanently forbidden SNPNs for access for localized services in the SNPN" per entry of a "list of subscriber data" and per Public Land Mobile Network (PLMN) subscription. Further, the MS use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription.

[0042] The MS adds the SNPN to the list of "temporarily forbidden SNPNs" for access of the localized services in the SNPN, if the SNPN is selected according to the SNPN selection criterion for the localized services as mentioned in the 3rdGeneration Partnership Project (3GPP) TS 23.122. The MS adds the SNPN to the list of "temporarily forbidden SNPNs" for onboarding services, if the MS is registered for the onboarding services in the SNPN or performing initial registration for the onboarding services in the SNPN.

[0043] The MS adds the SNPN to the list of "temporarily forbidden SNPNs" when the MS supports access to the SNPN using credentials from a credentials holder (CH), or / and equivalent SNPNs. Both the SNPN using the credentials from the CH and the equivalent SNPNs are associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. A message with cause value #74 is received by the MS in response to an location request (LR) from the SNPN. The message with cause value #74 reads "Temporarily not authorized for this SNPN".

[0044] In addition, if the message is integrity-protected, or if 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. Then the MS starts a MS implementation specific timer that is not shorter than 60 minutes.

[0045] Further, the 3GPP has introduced the concept of localized / local services. The localized service is a service which is localized. The localized services are 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, IMS, etc), or connectivity (e.g. UE to UE, UE to Data Network, etc.). A service provider that provides such a service is called a localized service provider. The localized service provider is an application provider or a network operator who make the services localized and offers to an end user via a hosting network.

[0046] A CH controlled prioritized list of the SNPNs and Group ID for Network Selection (GIN) are provided for the localized services in the SNPN. If the MS supports access to an SNPN providing access for the localized services in the SNPN, then the SNPN selection parameters for access for localized services in the SNPN. The selection of the SNPN parameters, consisting of:

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

[0048] a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains an GIN and a validity information consisting of time validity information.

[0049] A steering of roaming SNPN selection information for localized services (SOR-SNPN-SI-LS) is provided in the SNPN. When the access for the localized services in the SNPN has been enabled, a provisioning information for the SNPN is selected by the MS. The MS supporting access to the SNPN providing access for the localized services in the SNPN includes:

[0050] a) the CH controlled prioritized list of the preferred SNPNs for access for the localized services in the SNPN, where each entry contains the SNPN identity and the validity information consisting of time validity information,

[0051] b) the CH controlled prioritized list of the preferred GINs for access of the localized services in the SNPN", where each entry contains the GIN and the validity information consisting of time validity information, or

[0052] c) both of the above.

[0053] For a validity condition, the validity information includes a time validity information and location validity information. That is, time periods defined by start and an end times, when access to the SNPN for accessing the localized services is allowed. Location validity consists of geo location and / or tracking areas or cells where the UE can get localized services.

[0054] The location assistance validity information includes a geolocation information, and / or, a tracking area information of serving networks (i.e. lists of TACs per PLMN ID or per PLMN ID and NID). The provisioning information for SNPN selection consisting of the credentials holder controlled prioritized list of preferred SNPNs, and the credentials holder controlled prioritized list of GINs.

[0055] The Group ID for Network Selection (GIN) identifies a group of CHs that are available from the SNPN. Further, as per TS 23.122, when the UE receives the SOR-SNPN-SI information, and the integrity check is successful, the ME deletes the SNPNs identified by the CHs controlled prioritized list of the preferred SNPNs or the CHs controlled prioritized list of the GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs". The ME deletes the SNPNs when the SNPNs are present in the list of the preferred SNPNs or the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNP".

[0056] The UE has added a first SNPN to the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". Further, the UE receives the SOR-SNPN-SI information as a part of steering of roaming information over a control plane. The SOR-SNPN-SI information includes the CHs controlled prioritized list of the GINs.

[0057] As per the requirement from TS 23.122, the UE deletes the first SNPN if the first SNPN is identified by the CH controlled prioritized list of the GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs". But it is not clear how it is possible for the UE to identify and delete the SNPN from list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs" based on the GIN(s) entries in the CH controlled prioritized list of the GINs.

[0058] The same issue exists when the UE has to delete the SNPN from the list of "temporarily forbidden SNPNs for access of the localized services in the SNPN" or "permanently forbidden SNPNs for access of the localized services in the SNPN" based on the GIN(s) entry in a CH controlled prioritized list of the GINs for the localized services in SNPN, which is received as part of the SOR-SNPN-SI-LS information from the network.

[0059] Thus, it is desired to address the above mentioned disadvantages or other shortcomings or at least provide a useful alternative.

[0060] The principal object of the embodiments herein is to provide a method and a UE for deleting a SNPN from a Forbidden SNPN list based on CH list GINs.

[0061] Another objective of the embodiment herein is to provide a UE that adds a SNPN ID along with GIN ID(s) while adding an SNPN to the Forbidden SNPN list.

[0062] Yet, another objective of the embodiment is to provide that the UE remembers that the UE selected the SNPN because of the SNPN broadcasted the GIN which was configured as part of the CH list GINs.

[0063] Yet, another objective of the embodiment herein is to provide that the UE receives a SOR-SNPN-SI or a SOR-SNPN-SI-LS information with an empty or a non-empty CH list GINs and delete all SNPNs from the Forbidden SNPN list.

[0064] Yet, another objective of the embodiment herein is to provide that the UE removes all the SNPNs from the Forbidden SNPN list based on an additional information from a network apparatus.

[0065] Yet, another objective of the embodiment herein is to provide that the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with empty CH list GINs, and non-empty CH list SNPNs.

[0066] Yet, another objective of the embodiment herein is to provide that the UE deletes all the entities from the Forbidden SNPN list.

[0067] Accordingly, the embodiment herein a method for deleting a SNPN from a forbidden SNPN list in a wireless network. The method includes receiving, by a User Equipment (UE), a reject cause from a network apparatus. Further, the method includes adding, by the UE, the SNPN to a Forbidden SNPN list along with a broadcasted Group identifier (ID) for network selection (GIN) by the SNPN, while receiving the reject cause from the network apparatus. Further, the method includes receiving, by the UE, at least one of: a SOR-SNPN-SI information and a SOR-SNPN-SI-LS information. Further, the method includes removing, by the UE, the SNPN from the Forbidden SNPN list based on the broadcasted GIN using at least one of: the received SOR-SNPN-SI and the received SOR-SNPN-SI-LS information.

[0068] In an embodiment, the forbidden SNPN list includes at least one of list of: "temporarily forbidden SNPNs", "permanently forbidden SNPNs", "temporarily forbidden SNPNs for access for a localized service in the SNPN" and "permanently forbidden SNPN for access for the localized service in the SNPN".

[0069] In an embodiment, the reject cause comprises at least one of: existing 5GMM cause for example #74 (Temporarily not authorized for this SNPN), #75 (Permanently not authorized for this SNPN) or new 5GMM cause for example "localized service not available".

[0070] In an embodiment, the UE adds a SNPN ID along with the GIN ID, while adding the SNPN to the Forbidden SNPN list, wherein the SNPN ID is a combination of a Public Land Mobile Network (PLMN) ID and network identifier (NID).

[0071] In an embodiment, the network apparatus is an Access and Mobility Management Function　(AMF) entity.

[0072] In an embodiment, whenever the network apparatus sends at least one of: the SOR-SNPN-SI and SOR-SNPN-SI-LS list to the UE, at least one of: the SOR-SNPN-SI and the SOR-SNPN-SI-LS list includes an indication to delete all the SNPN(s) in the forbidden SNPN list.

[0073] Accordingly, the embodiment herein a UE for deleting a SNPN from a forbidden SNPN list in a wireless network. The UE includes a SNPN controller communicatively coupled to a memory and a processor. The SNPN controller is configured to receive a reject cause from a network apparatus. Further, the SNPN controller is configured to add the SNPN to a Forbidden SNPN list along with a broadcasted GIN by the SNPN, while receiving the reject cause from the network apparatus. Further, the SNPN controller is configured to receive at least one of: a SOR-SNPN-SI information and a SOR-SNPN-SI-LS information. Further, the SNPN controller is configured to remove the SNPN from the Forbidden SNPN list, based on the broadcasted GIN using at least one of: the received SOR-SNPN-SI and the received SOR-SNPN-SI-LS information.

[0074] Accordingly, the embodiment herein a method for deleting a SNPN from a forbidden SNPN list in a wireless network. The method includes receiving, by a network apparatus, a SNPN Registration request message from a UE. Further, the method includes creating, by the network apparatus, a reject cause comprising at least one of a 5GMM cause #74 and #75, an existing 5GMM cause" and a new 5GMM cause for the "localized service not available in SNPN. Further, the method includes sending, by the network apparatus, the reject cause to the UE.

[0075] In an embodiment, further, the method includes sending, by the network apparatus, at least one of: a SOR-SNPN-SI and a SOR-SNPN-SI-LS list to the UE, where at least one of: the SOR-SNPN-SI and the SOR-SNPN-SI-LS list includes an indication to delete all the SNPN in the forbidden SNPN list.

[0076] Accordingly, the embodiment herein a network apparatus for deleting a SNPN from a forbidden SNPN list in a wireless network. The network apparatus includes a SNPN controller communicatively coupled to a memory and a processor. The SNPN controller is configured to receive a SNPN Registration request message from a UE. Further, the SNPN controller is configured to create a reject cause comprising at least one of a 5GMM cause #74 and #75, an existing 5GMM cause and a new 5GMM cause for the "localized service not available in SNPN. Further, the SNPN controller is configured to send the reject cause to the UE.

[0077] 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 may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0078] Accordingly, the embodiment herein discloses a method for deleting a SNPN from a forbidden SNPN list in a wireless network. The method includes receiving, by a UE, a reject cause from a network apparatus. Further, the method includes adding, by the UE, the SNPN to a Forbidden SNPN list along with a broadcasted GIN by the SNPN, while receiving the reject cause from the network apparatus. Further, the method includes receiving, by the UE, at least one of: a SOR-SNPN-SI information and a SOR-SNPN-SI-LS information. Further, the method includes removing, by the UE, the SNPN from the Forbidden SNPN list based on the GIN indicated in at least one of: the received SOR-SNPN-SI and the received SOR-SNPN-SI-LS information.

[0079] The method entails the deletion of SNPN from the forbidden SNPN list through the use of GIN. When the UE adds an SNPN ID to the forbidden SNPN list, it includes the broadcasted GIN(s) as well. The SNPN subsequently broadcasts the added GIN(s). Later, when the UE receives a SOR-SNPN-SI or a SOR-SNPN-SI-LS with non-empty CH list GINs from an AMF entity, it removes all SNPNs based on the saved GIN(s) from the forbidden SNPN list. The UE maintains a record of its attempt to remove the SNPN when the broadcasted GIN(s) were configured in the CH list GINs. Upon receiving the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with a non-empty CH list GINs from the AMF entity, the UE eliminates all the SNPNs earlier added to the Forbidden SNPN list.

[0080] In an embodiment, whenever the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with empty CH list GINs, but the non-empty CH list SNPNs deletes all the entries from the Forbidden SNPN list.

[0081] In an embodiment, whenever a network sends the SOR-SNPN-SI or the SOR-SNPN-SI-LS information to the UE, the network ensures to include combination of GIN and SNPN(s) that broadcasts the same GIN(s) as part of the CH list GINs.

[0082] In an embodiment, whenever the network sends the SOR-SNPN-SI or SOR-SNPN-SI-LS list to the UE, where the SOR-SNPN-SI or SOR-SNPN-SI-LS list optionally includes an indication to delete all the SNPN(s) in the Forbidden SNPN list.

[0083] In an embodiment, the UE remembers that the UE had attempted in the SNPN because one or more of the broadcasted GIN(s) by the SNPN were configured in the CH list GINs. Later when the network apparatus sends the SOR-SNPN-SI or the SOR-SNPN-SI-LS information to the UE, the SOR-SNPN-SI or SOR-SNPN-SI-LS list include an optional indication to delete all the SNPN(s) from the Forbidden SNPN list that were tried because the SNPNs broadcasted GINs present in the CH list GINs is configured in the UE.

[0084] In an embodiment, the Forbidden SNPN list is referred to "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs" or "temporarily forbidden SNPNs for access for localized services in the SNPN" and "permanently forbidden SNPNs for access for localized services in SNPN" or all of them.

[0085] In an embodiment, the Reject cause is referred to #74 or #74 or other existing 5GMM causes as well, or new 5GMM cause like #XX (Localized service not available") which can lead to the UE adding the SNPN to the Forbidden SNPN list.

[0086] In an embodiment, the CH list GINs refers to "credentials holder controlled prioritized list of GIN(s)" or "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" or both.

[0087] In an embodiment, the CH list SNPNs is referred to "credentials holder controlled prioritized list of SNPN(s)" or "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or both.

[0088] In an embodiment, while adding the SNPN to the Forbidden SNPN list, the UE adds the SNPN ID i.e. (combination of PLMN-ID and NID) along with the GIN(s) that is broadcasted by the SNPN. Later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the non-empty CH list GINs, the UE removes all the SNPNs based on the saved GIN(s) from Forbidden SNPN list. The saved GIN(s) are based on the entries of GIN(s) received in the CH list GINs.

[0089] For example, when the UE attempted registration in the first SNPN because the first SNPN is broadcasted in the first GIN, second GIN etc., and the UE had attempted in the first SNPN because the first GIN or the second GIN or both are configured in CH list GINs or because the SNPN is configured in the CH list of SNPNs. Later when the UE receives a reject from the AMF entity with a Reject cause then, the UE adds 'combination of first SNPN and first GIN and second GIN" or "combination of first SNPN and first GIN and combination of first SNPN and second GIN" in the Forbidden SNPN list. Later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the CH list GINs, having the first GIN as an entry. The UE removes the first SNPN and all other SNPNs from the Forbidden SNPN list, the Forbidden SNPN list that have first GIN as an entry in the Forbidden SNPN list.

[0090] In an embodiment, the UE remembers that the UE has attempted in the SNPN because one or more of the broadcasted GIN(s) by the SNPN are configured in the CH list GINs. Later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS optionally with the non-empty the CH list GINs, the UE removes all such SNPNs that were added to Forbidden SNPN list earlier.

[0091] For example, when the UE has already attempted registration in the first SNPN because the first SNPN was broadcasted in the first GIN, second GIN etc., and the UE has already attempted in the first SNPN because the first GIN or the second GIN or both are configured in the CH list GINs, and the UE receives the reject from the AMF entity with the Reject cause the UE adds the first SNPN to the Forbidden SNPN list. Further, the UE remembers that the first SNPN was attempted due to the GIN entry in the CH list GINs. Later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS optionally with non-empty the CH list GINs list, the UE removes the first SNPN and all the other SNPNs from the Forbidden SNPN list that were originally attempted due to broadcasted GIN(s) matching the entries in the CH list GINs.

[0092] In an embodiment, whenever the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS optionally with the non-empty CH list GINs, the UE deletes all the entries from the Forbidden SNPN list.

[0093] For example, When the UE attempted registration in the first SNPN, second SNPN and etc. then on receiving a reject from the AMF entity with Reject cause the UE adds the "combination of first SNPN and first GIN and second GIN" in the Forbidden SNPN list. Later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the non-empty CH list GINs list, then the UE remove the first SNPN, second SNPN and all other SNPNs from the Forbidden SNPN list.

[0094] In an embodiment, whenever the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the empty CH list GINs, but non-empty CH list SNPNs then the UE deletes all the entries from the Forbidden SNPN list.

[0095] For example, when the UE attempted registration in the first SNPN, second SNPN and etc. then on receiving a reject from the AMF entity with Reject cause the UE adds the "combination of first SNPN and first GIN and second GIN" in the Forbidden SNPN list. Later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the empty CH list GINs but the non-empty CH list SNPNs list, then the UE removes the first SNPN, second SNPN and all other SNPNs from the Forbidden SNPN list.

[0096] In an embodiment, whenever the network apparatus sends the SOR-SNPN-SI or the SOR-SNPN-SI-LS information to the UE, the network apparatus ensures to include the combination of GIN and SNPN(s) as part of the CH list GINs. Where the SNPN(s) that broadcasts the same GIN(s), which means the following:

[0097] a. The UE can access the SNPN if the broadcasted GIN / GIN(s) of the SNPN and the SNPN ID of the SNPN is part of the CH list GINs. That is, if the CH list GINs has the combination of first SNPN and first GIN only, then the UE access the first SNPN if GIN / GIN(s) of the SNPN broadcasts the first GIN. If there is another SNPN in the area, say second SNPN broadcasting first GIN, and then the UE cannot access the second SNPN as it is not configured in CH list GINs.

[0098] b. The combination of SNPN ID and GIN ID is used by the UE to save in the Forbidden SNPN list as explained in point (i) after receiving the reject with the Reject cause.

[0099] c. The SNPN ID and GIN ID combination received in the CH list GINs is used by the UE to remove the corresponding SNPN ID and the GIN ID from the Forbidden SNPN list. i.e. if the combination of first SNPN and first GIN and combination of second SNPN and first GIN are present, and the network apparatus sends the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the CH list GINs entry that has the combination of first SNPN and first GIN and combination of second SNPN and second GIN, then the UE removes the combination of first SNPN and first GIN combination from Forbidden SNPN list.

[0100] In an embodiment, whenever the network apparatus sends the SOR-SNPN-SI or the SOR-SNPN-SI-LS information to the UE, the SOR-SNPN-SI or the SOR-SNPN-SI-LS information optionally includes an indication to delete all the SNPN(s) in the Forbidden SNPN list.

[0101] For example, when the UE adds the first SNPN, second SNPN etc. due to the received reject from the AMF entity with Reject cause, the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the optional indication to delete all entries in Forbidden SNPN list. The UE deletes the first SNPN, and second SNPN based on the received from the list of Forbidden SNPN list based on the additional indication from the network apparatus.

[0102] In an embodiment, the UE remembers that the UE had attempted in the SNPN because one or more of the broadcasted GIN(s) by the SNPN were configured in the CH list GINs. Later when the network apparatus sends the SOR-SNPN-SI or the SOR-SNPN-SI-LS information to the UE. The received SOR-SNPN-SI or the SOR-SNPN-SI-LS list includes an optional indication to delete all the SNPN(s) (from Forbidden SNPN list) which were tried because the SNPNs broadcasted GINs present in the CH list GINs that is configured in the UE.

[0103] For example when the UE attempted registration in the first SNPN because the first SNPN was broadcasting the first GIN, second GIN and etc. Further, the UE had attempted in the first SNPN because the first GIN or the second GIN or both are configured in the CH list GINs, then on receiving a reject from the AMF entity with Reject cause the UE adds the first SNPN to the Forbidden SNPN list. Further, the UE remembers that the first SNPN was attempted due to the GIN entry in the CH list GINs. Then later when the UE receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the optional indication to delete such SNPNs, the UE deletes the first SNPN from the Forbidden SNPN list.

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

[0105] FIG. 1 is a flow chart that illustrates the inadequacy of prior art in enabling a UE to delete the first SNPN with reference to a first GIN entry in a CH controlled prioritized list of GINs, according to prior art.

[0106] The UE (100) is registered in a second SNPN, while the first SNPN is either listed as "temporarily forbidden SNPNs" or "permanently forbidden SNPNs" due to reject causes #74 (Temporarily not authorized for this SNPN) or #75 (Permanently not authorized for this SNPN). Despite not being in the CH controlled prioritized list of SNPN(s), the UE (100) attempts to register in the first SNPN as it broadcasts the GIN configured in the list of GIN(s), such as first GIN. Subsequently, the UE (100) receives SOR-SNNP-SI information from the network containing the CH controlled prioritized list of GIN(s) with entries first GIN and second GIN. However, the UE (100) is unable to remove the first SNPN based on the first GIN entry in the list of GIN(s) as per the SOR-SNNP-SI information received.

[0107] Further the above cited problems are not restricted to the SNPNs alone, but to the equivalent SNPNs as well. The lists are not restricted to the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs" or CH controlled prioritized list of the GIN(s) but is applicable to the list of the Forbidden SNPN list and CH list GINs.

[0108] The reject causes are not restricted to #74 or #75 but to other existing 5thGeneration Mobility Management (5GMM) causes as well, or new 5GMM cause like #XX (Localized service not available") which can lead to the UE (100) adding the SNPN to the list of the Forbidden SNPN list. Further the SOR-SNNP-SI list can be extended to the SOR-SNNP-SI-LS as well.

[0109] At step 1, the first SNPN broadcasts the first GIN, and the first GIN is configured in the credential`s holder controlled prioritized list of GINs. At step 2, the UE (100) sends the first SNPN registration request to the AMF entity (200). At step 3, the UE (100) receives the registration reject with cause #74 "Temporarily not authorized for this SNPN" or #75 "Permanently not authorized for this SNPN" from the AMF entity (200). At step 4, the UE (100) adds the first SNPN to "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". At step 5, the UE (100) receives the SOR-SNPN-SI information SOR-SNPN-SI entry including the credentials holder controlled prioritized list of GIN(s) with entries first GIN, second GIN from the AMF entity (200). At step 6, the UE (100) does not know how to delete first SNPN based on first GIN entry in Credentials holder controlled prioritized list of GIN(s) received at step 5.

[0110] FIG. 2 is a flow chart that illustrates to operations undertaken by the UE to eliminate the first SNPN from a prohibited SNPN list, following the receipt of a first GIN entity in a wireless network (1000), according to the embodiments as disclosed herein.

[0111] At step 1, the first SNPN broadcasts first GIN, by the UE (100) and the first GIN is configured in CH list GINs. At step 2, the UE (100) sends a registration request in the first SNPN to an AMF entity (200). At step 3, the AMF entity (200) sends the registration reject with the Reject cause to the UE (100). At step 4, the UE (100) adds the combination of first SNPN and first GIN to the Forbidden SNPN list. At step 5, when the UE (100) registers in the second SNPN, then the UE (100) receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with entry like CH list GINs that includes entries like the first GIN, and the second GIN. At step 6, based on the received first GIN entry in SOR-SNPN-SI or SOR-SNPN-SI-LS information, the UE (100) removes the first SNPN from the Forbidden SNPN list.

[0112] FIG. 3 is a flow chart that illustrates technical operations performed by the UE (100) to remove the first SNPN from the forbidden SNPN list that were attempted due to a broadcasted GIN matching entry in the CH list GINs earlier in the wireless network (1000), according to the embodiments as disclosed herein.

[0113] At step 1, the first SNPN broadcasts first GIN, by the UE (100) and the first GIN configured in CH list GINs. At step 2, the UE (100) sends a registration request in the first SNPN to the AMF entity (200). At step 3, the AMF entity (200) sends the registration reject with cause Reject cause to the UE (100). At step 4, the UE (100) adds the first SNPN to the Forbidden SNPN list and remembers that the first SNPN was attempted due to the GIN entry configured in the CH list GINs. At step 5, when the UE (100) registers in the second SNPN, then the UE (100) receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with non-empty CH list GINs. At step 6, the UE (100) removes the first SNPN from the Forbidden SNPN list and all other SNPNs from Forbidden SNPN list that were attempted due to the broadcasted GIN matching entry in the CH list GINs earlier.

[0114] FIG. 4 is a flow chart illustrating technical operations performed by the UE (100) to remove all the entries from the forbidden SNPN list in the wireless network (1000), according to the embodiments as disclosed herein.

[0115] At step 1, the first SNPN broadcasts first GIN, by the UE (100) and the first GIN configured in CH list GINs. The UE (100) camps in first SNPN. At step 2, the UE (100) sends a registration request in the first SNPN to the AMF entity (200). At step 3, the AMF entity (200) sends the registration reject with cause Reject cause to the UE (100). At step 4, the UE (100) adds the first SNPN to the Forbidden SNPN list and later the UE (100) registers in the second SNPN. At step 5, the UE (100) receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with non-empty CH list GINs. At step 6, the UE (100) removes all the entities form the Forbidden SNPN list including the first SNPN.

[0116] FIG. 5 is a flow chart illustrating technical operations performed by the UE (100) to remove all the entries from the forbidden SNPN list, with empty CH list GINs but the non-empty CH list SNPNs in the wireless network (1000), according to the embodiments as disclosed herein.

[0117] At step 1, the UE (100) camps on the first SNPN and sends a registration request in the first SNPN to the AMF entity (200) at step 2. At step 3, the AMF entity (200) sends the registration reject with cause Reject cause to the UE (100). At step 4, the UE (100) adds the first SNPN to the Forbidden SNPN list and later the UE (100) registers in the second SNPN. At step 5, the UE (100) receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the empty CH list GINs but the non-empty CH list SNPNs. At step 6, the UE (100) removes all the entities form the Forbidden SNPN list including the first SNPN.

[0118] FIG. 6 is a flow chart illustrating technical operations performed by the UE (100) to remove combination a first SNPN and a first GIN from the Forbidden SNPN list in the wireless network (1000), according to the embodiments as disclosed herein.

[0119] At step 1, the first SNPN broadcasts first GIN, by the UE (100) and the combination of first SNPN and first GIN configured in the CH list GINs. At step 2, the UE sends a registration request in the first SNPN to the AMF entity (200). At step 3, the AMF entity (200) sends the registration reject with cause Reject cause to the UE (100). At step 4, the UE (100) adds the combination of first SNPN and first GIN combination to the Forbidden SNPN list and later the UE (100) registers in the second SNPN. At step 5, the UE (100) receives the SOR-SNPN-SI or the SOR-SNPN-SI-LS information with the non-empty CH list GINs. The CH list GINs includes the combination of the combination of first SNPN and first GIN and the combination of second SNPN and second GIN. At step 6, the UE (100) removes combination of first SNPN and first GIN form the Forbidden SNPN list, based on the entries in the received CH list GINs.

[0120] FIG. 7 shows various hardware components of the UE (100), according to the embodiments as disclosed herein. The UE (100) may be, but not limited to a laptop, a palmtop, a desktop, a mobile phone, a smart phone, a Personal Digital Assistant (PDA), a tablet, a wearable device, an Internet of Things (IoT) device, a virtual reality device, a Video see through (VST), an augmented reality (AR) glass, a foldable device, a flexible device, a display device and an immersive system. In an embodiment, the UE (100) includes a processor (110), a communicator (120), a memory (130) and a SNPN controller (140). The processor (110) is coupled with the communicator (120), the memory (130) and the SNPN controller (140).

[0121] The SNPN controller(140) may be a part of the processor (110). The processor (110) may include the SNPN controller (140).

[0122] The SNPN controller (140) receives the reject cause from the network apparatus (e.g., AMF entity or the like) (200). Further, the SNPN controller (140) adds the SNPN to the Forbidden SNPN list along with the broadcasted GIN by the SNPN, while receiving the reject cause from the network apparatus (200). In an embodiment, the forbidden SNPN list comprises at least one of list of: "temporarily forbidden SNPNs", "permanently forbidden SNPNs", "temporarily forbidden SNPNs for access for the localized service in the SNPN and the "permanently forbidden SNPN" for access for the localized service in the SNPN. In an embodiment, the reject cause comprises at least one of: the 5GMM cause #74, the existing 5GMM cause and the 5GMM cause for the "localized service not available".

[0123] Further, the SNPN controller (140) receives at least one of: the SOR-SNPN-SI information and the SOR-SNPN-SI-LS information. Further, the SNPN controller (140) removes the SNPN from the Forbidden SNPN list, based on the broadcasted GIN using at least one of: the received SOR-SNPN-SI and the received SOR-SNPN-SI-LS information.

[0124] In an embodiment, the SNPN controller (140) adds the SNPN ID along with the GIN ID, while adding the SNPN to the Forbidden SNPN list, where the SNPN ID is a combination of the PLMN ID and NID.

[0125] The SNPN 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 and the like, and may optionally be driven by firmware.

[0126] The processor (110) may include one or a plurality of processors. The one or the 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (110) may include multiple cores and is configured to execute the instructions stored in the memory (130).

[0127] Further, the processor (110) is configured to execute instructions stored in the memory (130) and to perform various processes. The communicator(120) is configured for communicating internally between internal hardware components and 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 discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (130) may, in some examples, 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 a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0128] In an embodiment, the communicator (120) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (120) is configured to communicate internally between internal hardware components of the UE (100) and with external devices via one or more networks.

[0129] Although the FIG. 7 shows various hardware components of the UE (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the UE (100).

[0130] FIG. 8 is a flow chart (S800) illustrating a method, implemented by the UE (100), for deleting the SNPN from the forbidden SNPN list in the wireless network (1000), according to the embodiments as disclosed herein. The wireless network (1000) can be, for example, but not limited to a fourth generation (4G) network, a fifth generation (5G) network, an Open Radio Access Network (ORAN) or the like. The operations (S802-S808) are handled by the SNPN controller (140).

[0131] At S802, the method includes receiving the reject cause from the network apparatus (200). At S804, the method includes adding the SNPN to the Forbidden SNPN list along with a broadcasted GIN by the SNPN, while receiving the reject cause from the network apparatus (200). At S806, the method includes receiving at least one of: the SOR-SNPN-SI information and the SOR-SNPN-SI-LS information. At S808, the method includes removing the SNPN from the Forbidden SNPN list based on the broadcasted GIN using at least one of: the received SOR-SNPN-SI and the received SOR-SNPN-SI-LS information.

[0132] FIG. 9 shows various hardware components of the network apparatus (200), according to the embodiments as disclosed herein. In an embodiment, the network apparatus (200) includes a processor (210), a communicator (220), a memory (230) and a SNPN controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the SNPN controller (240).

[0133] The network apparatus may correspond to a network entity. The network apparatus may be referred to as the network entity.

[0134] The SNPN controller (240) receives the SNPN registration request message from the UE (100). Further, the SNPN controller (240) creates the reject cause including at least one of the 5GMM cause #74 and #75, the existing 5GMM cause and the new 5GMM cause for the "localized service not available. Further, the SNPN controller (240) sends the reject cause to the UE (100) in SNPN. Further, the SNPN controller (240) sends at least one of: the SOR-SNPN-SI and the SOR-SNPN-SI-LS list to the UE (100), where at least one of: the SOR-SNPN-SI and the SOR-SNPN-SI-LS list includes the indication to delete all the SNPN in the forbidden SNPN list.

[0135] The SNPN controller (240) 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 and the like, and may optionally be driven by firmware.

[0136] The processor (210) may include one or a plurality of processors. The one or the 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (230).

[0137] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator(220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such 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. In addition, the memory (230) may, in some examples, 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 a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0138] The SNPN controller(240) may be a part of the processor (210). The processor (210) may include the SNPN controller (240).

[0139] In an embodiment, the communicator (220) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (220) is configured to communicate internally between internal hardware components of the network apparatus (200) and with external devices via one or more networks.

[0140] Although the FIG. 9 shows various hardware components of the network apparatus (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the network apparatus (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the network apparatus (200).

[0141] FIG. 10 is a flow chart (S1000) illustrating a method, implemented by the network apparatus (200), for deleting the SNPN from the forbidden SNPN list in the wireless network (1000), according to the embodiments as disclosed herein.

[0142] At S1002, the method includes receiving the SNPN registration request message from the UE (100). At S1004, the method includes creating the reject cause including at least one of the 5GMM cause #74 and #75, the existing 5GMM cause and a new 5GMM cause for the "localized service not available in SNPN. At S1006, the method includes sending the reject cause to the UE (100).

[0143] The problem and solution statements in the above embodiments are not restricted to registration reject alone, but to all possible NAS messages which can come from the network apparatus (200), or the NAS procedures which can get rejected by the network apparatus (200) with the Reject cause.

[0144] The various actions, acts, blocks, steps, or the like in the flow chart (S800 and S1000) may be 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 may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0145] The embodiments disclosed herein can be implemented using at least one hardware device and performing network management functions to control the elements.

[0146] 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 should and 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.

[0147] According to an embodiment of the disclosure, a method performed by a user equipment(UE) may include in case that the UE supports access to at least one stand alone non-public network(SNPN), storing at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list.

[0148] According to an embodiment of the disclosure, the method may include receiving, from a network, a steering of roaming(SOR) information.

[0149] According to an embodiment of the disclosure, the method may include in case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), deleting SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.

[0150] According to an embodiment of the disclosure, wherein the forbidden SNPN list comprises at least one of list of temporarily forbidden SNPNs, permanently forbidden SNPNs, temporarily forbidden SNPN for access for a localized service in the SNPN, and permanently forbidden SNPNs for access for the localized service in the SNPN.

[0151] According to an embodiment of the disclosure, the method may include receiving, from the network, a reject message.

[0152] According to an embodiment of the disclosure, the method may include storing the at least one SNPN ID and the at least one broadcasted GIN to the forbidden SNPN list based on the reject message.

[0153] According to an embodiment of the disclosure, wherein at least one of the SOR-SNPN-SI or the SOR-SNPN-SI-LS includes a credentials holder controlled prioritized list of at least one GIN.

[0154] According to an embodiment of the disclosure, the method may include deleting the SNPN ID from the forbidden SNPN list in cast that the GIN is identified by the credentials holder controlled prioritized list of at least one GINs.

[0155] According to an embodiment of the disclosure, the method may include verifying that the SOR information is transmitted from the SNPN.

[0156] According to an embodiment of the disclosure, the method may include deleting the SNPN ID from the forbidden SNPN list based on the verification.

[0157] According to an embodiment of the disclosure, wherein the at least one broadcasted GIN is broadcasted by the at least one SNPN. According to an embodiment of the disclosure, a method performed by a network entity may include transmitting, to a user equipment(UE), a reject message.

[0158] According to an embodiment of the disclosure, wherein the reject message is used, at the UE, to store the at least one stand alone non-public network(SNPN) identifier ID and the at least one broadcasted group ID for network selection (GIN) to the forbidden SNPN list.

[0159] According to an embodiment of the disclosure, the method may include transmitting, to the UE, a steering of roaming(SOR) information.

[0160] According to an embodiment of the disclosure, wherein the SOR information is used, at the UE, to delete the at least one SNPN ID from the forbidden SNPN list based on the at least one broadcasted GIN, and at least one of SOR-SNPN-selection information(SOR-SNPN-SI) or SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS) in case that the SOR information includes the at least one of SOR-SNPN-SI or SOR-SNPN-SI-LS.

[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 further configured to in case that the UE supports access to at least one stand alone non-public network(SNPN), store at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list.

[0163] According to an embodiment of the disclosure, wherein the processor is further configured to receive, from a network, a steering of roaming(SOR) information.

[0164] According to an embodiment of the disclosure, wherein the processor is further configured to in case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), delete SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.

[0165] According to an embodiment of the disclosure, wherein the forbidden SNPN list comprises at least one of list of temporarily forbidden SNPNs, permanently forbidden SNPNs, temporarily forbidden SNPN for access for a localized service in the SNPN, and permanently forbidden SNPNs for access for the localized service in the SNPN.

[0166] According to an embodiment of the disclosure, wherein the processor is further configured to receive, from the network, a reject message.

[0167] According to an embodiment of the disclosure, wherein the processor is further configured to store the at least one SNPN ID and the at least one broadcasted GIN to the forbidden SNPN list based on the reject message.

[0168] According to an embodiment of the disclosure, wherein at least one of the SOR-SNPN-SI or the SOR-SNPN-SI-LS includes a credentials holder controlled prioritized list of at least one GIN.

[0169] According to an embodiment of the disclosure, wherein the processor is further configured to delete the SNPN ID from the forbidden SNPN list in cast that the GIN is identified by the credentials holder controlled prioritized list of at least one GINs.

[0170] According to an embodiment of the disclosure, wherein the processor is further configured to verify that the SOR information is transmitted from the SNPN.

[0171] According to an embodiment of the disclosure, wherein the processor is further configured to delete the SNPN ID from the forbidden SNPN list based on the verification.

[0172] According to an embodiment of the disclosure, wherein the at least one broadcasted GIN is broadcasted by the at least one SNPN.

[0173] According to an embodiment of the disclosure, a network entity may include may include a transceiver and a processor coupled with the transceiver.

[0174] According to an embodiment of the disclosure, wherein the processor is further configured to transmit, to a user equipment(UE), a reject message.

[0175] According to an embodiment of the disclosure, wherein the reject message is used, at the UE, to store the at least one stand alone non-public network(SNPN) identifier ID and the at least one broadcasted group ID for network selection (GIN) to the forbidden SNPN list.

[0176] According to an embodiment of the disclosure, wherein the processor is further configured to transmit, to the UE, a steering of roaming(SOR) information.

[0177] According to an embodiment of the disclosure, wherein the SOR information is used, at the UE, to delete the at least one SNPN ID from the forbidden SNPN list based on the at least one broadcasted GIN, and at least one of SOR-SNPN-selection information(SOR-SNPN-SI) or SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS) in case that the SOR information includes the at least one of SOR-SNPN-SI or SOR-SNPN-SI-LS.

Claims

1.A method performed by a user equipment(UE), the method comprising:in case that the UE supports access to at least one stand alone non-public network(SNPN), storing at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list;receiving, from a network, a steering of roaming(SOR) information; andin case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), deleting SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.2.The method of claim 1, wherein the forbidden SNPN list comprises at least one of list of temporarily forbidden SNPNs, permanently forbidden SNPNs, temporarily forbidden SNPN for access for a localized service in the SNPN, and permanently forbidden SNPNs for access for the localized service in the SNPN.3.The method of claim 1, further comprising:receiving, from the network, a reject message, andwherein the storing the at least one SNPN ID and the at least one broadcasted GIN to the forbidden SNPN list comprising:storing the at least one SNPN ID and the at least one broadcasted GIN to the forbidden SNPN list based on the reject message.4.The method of claim 1,wherein at least one of the SOR-SNPN-SI or the SOR-SNPN-SI-LS includes a credentials holder controlled prioritized list of at least one GIN,wherein the deleting the SNPN ID from the forbidden SNPN list comprising:deleting the SNPN ID from the forbidden SNPN list in cast that the GIN is identified by the credentials holder controlled prioritized list of at least one GINs.5.The method of claim 1, wherein the deleting the SNPN ID from the forbidden SNPN list comprising:verifying that the SOR information is transmitted from the SNPN; anddeleting the SNPN ID from the forbidden SNPN list based on the verification.6.The method of claim 1, wherein the at least one broadcasted GIN is broadcasted by the at least one SNPN.7.A method performed by a network entity, the method comprising:transmitting, to a user equipment(UE), a reject message;wherein the reject message is used, at the UE, to store the at least one stand alone non-public network(SNPN) identifier ID and the at least one broadcasted group ID for network selection (GIN) to the forbidden SNPN list;transmitting, to the UE, a steering of roaming(SOR) information;wherein the SOR information is used, at the UE, to delete the at least one SNPN ID from the forbidden SNPN list based on the at least one broadcasted GIN, and at least one of SOR-SNPN-selection information(SOR-SNPN-SI) or SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS) in case that the SOR information includes the at least one of SOR-SNPN-SI or SOR-SNPN-SI-LS.8.A user equipment(UE), comprising:a transceiver; anda processor coupled with the transceiver, configured to:in case that the UE supports access to at least one stand alone non-public network(SNPN), store at least one SNPN identifier(ID) along with at least one broadcasted group ID for network selection (GIN) to a forbidden SNPN list;receive, from a network, a steering of roaming(SOR) information; andin case that the SOR information includes at least one of a SOR SNPN selection information(SOR-SNPN-SI) or a SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS), delete SNPN ID from the forbidden SNPN list based on GIN identified based on at least one of SOR-SNPN-SI or the SOR-SNPN-SI-LS.9.The UE of claim 8, wherein the forbidden SNPN list comprises at least one of list of temporarily forbidden SNPNs, permanently forbidden SNPNs, temporarily forbidden SNPN for access for a localized service in the SNPN, and permanently forbidden SNPNs for access for the localized service in the SNPN.10.The UE of claim 8, wherein the processor is further configured to:receive, from the network, a reject message, andstore the at least one SNPN ID and the at least one broadcasted GIN to the forbidden SNPN list based on the reject message.11.The UE of claim 8,wherein at least one of the SOR-SNPN-SI or the SOR-SNPN-SI-LS includes a credentials holder controlled prioritized list of at least one GIN,wherein the processor is further configured to:delete the SNPN ID from the forbidden SNPN list in cast that the GIN is identified by the credentials holder controlled prioritized list of at least one GINs.12.The UE of claim 8, wherein the processor is further configured to:verify that the SOR information is transmitted from the SNPN; anddelete the SNPN ID from the forbidden SNPN list based on the verification.13.The UE of claim 8, wherein the at least one broadcasted GIN is broadcasted by the at least one SNPN.14.A network entity, comprising:a transceiver; anda processor coupled with the transceiver, configured to:transmit, to a user equipment(UE), a reject message;wherein the reject message is used, at the UE, to store the at least one stand alone non-public network(SNPN) identifier ID and the at least one broadcasted group ID for network selection (GIN) to the forbidden SNPN list;transmit, to the UE, a steering of roaming(SOR) information;wherein the SOR information is used, at the UE, to delete the at least one SNPN ID from the forbidden SNPN list based on the at least one broadcasted GIN, and at least one of SOR-SNPN-selection information(SOR-SNPN-SI) or SOR-SNPN-SI for localized services(SOR-SNPN-SI-LS) in case that the SOR information includes the at least one of SOR-SNPN-SI or SOR-SNPN-SI-LS.

Images