Method and apparatus for managing forbidden lists of tracking areas (TAS) in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Disclosed subject matter relates to method and UE for managing forbidden lists of TAs in wireless communication system. According to an embodiment of the present disclosure, a method performed by a user equipment, UE, in a wireless communication system comprises receiving, from an access and mobility management function (AMF) entity of a first stand-alone non-public network (SNPN) selected for a localized service, a registration reject message of a first registration procedure, the registration reject message including a mobility management (MM) reject cause, and storing, based on the MM reject cause, a current tracking area identity (TAI) of a tracking area (TA) in a forbidden TA list for the first SNPN and a selected entry of list of subscriber data or a selected PLMN subscription along with a group identification for network (GIN).

Description

METHOD AND APPARATUS FOR MANAGING FORBIDDEN LISTS OF TRACKING AREAS (TAS) IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates to the field of communication networks. More specifically, the present disclosure relates to a method and an apparatus for managing forbidden lists of Tracking Areas (TAs) in wireless communication systems.

[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 (THz) 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] The present disclosure relates generally to wireless communication systems. More specifically, the present disclosure relates to a method and an apparatus for managing forbidden lists of Tracking Areas (TAs) in wireless communication systems

[0009] According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication system.

[0010] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0011] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and / or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:

[0012] Fig. 1 shows an exemplary environment for managing forbidden lists of Tracking Areas (TAs) in communication networks, in accordance with some embodiments of the present disclosure;

[0013] Fig. 2 shows a detailed block diagram of a User Equipment (UE), in accordance with some embodiments of the present disclosure.

[0014] Fig. 3 shows a sequence diagram for managing forbidden lists of Tracking Areas (TAs), in accordance with some embodiments of the present disclosure;

[0015] Fig. 4 shows a flowchart illustrating a method for managing forbidden lists of Tracking Areas (TAs), in accordance with some embodiments of the present disclosure;

[0016] Fig. 5 is a block diagram of an exemplary system for implementing embodiments consistent with the present disclosure;

[0017] FIG. 6 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure;

[0018] FIG. 7 is a block diagram of a base station (BS) according to an embodiment of the disclosure; and

[0019] FIG. 8 is a block diagram of a network entity according to an embodiment of the disclosure.

[0020] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0021] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0022] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0023] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0024] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0025] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0026] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0027] As used in embodiments of the disclosure, a “~unit” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit” does not always have a meaning limited to software or hardware. The “~unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit” may be either combined into a smaller number of components and a “~unit,” or divided into additional components and a “~unit.” Moreover, the components and “~units” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit” may include one or more processors.

[0028] 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 instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0029] 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, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0030] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0031] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0032] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0033] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0034] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0035] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0036] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0037] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0038] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0039] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0040] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0041] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0042] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0043] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0044] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure.

[0045] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0046] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0047] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0048] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0049] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0050] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0051] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0052] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0053] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project　(3GPP) technical specifications (TS) where appropriate.

[0054] Hereinafter, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a BS controller, or a node on a network.

[0055] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0056] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0057] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a UE, and an uplink (UL) refers to a radio link through which a UE transmits a signal to a BS.

[0058] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0059] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0060] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling.

[0061] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0062] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0063] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0064] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0065] While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however, that it is not intended to limit the disclosure to the forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.

[0066] The terms “comprises,” “comprising,” “includes” or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that includes a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises... a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.

[0067] In a communication network, User Equipment (UEs) connect based on geographical areas in which the UEs are located, referred as Tracking Areas (TAs). Notably, each TA comprises an identity within the communication network, referred as a Tracking Area Identity (TAI), which is used to identify TAs. The TAI is constructed from the Mobile Country Code (MCC), Mobile Network Code (MNC) and Tracking Area Code (TAC).

[0068] When a rejection is received by the UEs during a registration procedure with Stand-alone Private Network (SNPN) cell, the TAC of the TA where the UE is located and which corresponds to a Group ID for Network selection (GIN) broadcasted by the UE, gets stored in a forbidden list of TAs. Typically, the registration procedure with the SNPN is rejected when the UE attempts to register in the TA where it is not authorized to operate within that specific SNPN. Currently, when the UE is successfully registered with another SNPN and if location validity information comprising the TAC corresponding to the same GIN is received, the said TAC cannot be utilized for availing localized services even in another SNPN by the UE. This is typically due to the TAC being stored in the forbidden list.

[0069] Currently, in such scenarios, the TAI may get stuck in the forbidden list of TAs and there exists no technique to remove the same, even after the cause for rejection has been rectified. As of now, the UE has no mechanism to identify the TAC using broadcasted GIN. This is because, when a TAC is added to the forbidden list, the broadcasted GIN of that SNPN is lost, and the UE does not remember the GIN broadcasted by the SNPN. Hence the associated GIN value of the TAC in the forbidden lists is also lost.

[0070] The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms prior art already known to a person skilled in the art.

[0071] One or more shortcomings of the prior art may be overcome, and additional advantages may be provided through the present disclosure. Additional features and advantages may be realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.

[0072] In a non-limiting embodiment of the disclosure, a method of managing forbidden lists of Tracking Areas (TAs) in communication networks is disclosed. The method comprises receiving during a registration procedure, a Mobility Management (MM) reject cause message indicative of a failure in User Equipment (UE) registration with a first Stand-alone Private Network (SNPN) cell selected to avail localized services in a Tracking Area (TA). The method further comprises adding at least one Group ID for Network (GIN) and a current Tracking Area Identity (TAI) comprising at least one Tracking Area Code (TAC) of the TA associated with the at least one GIN broadcasted by the first SNPN cell, to a forbidden list among a plurality of forbidden lists associated with the first SNPN cell, upon receiving the MM reject cause message. Furthermore, the method comprises receiving Steering of Roaming SNPN Selection Information for Localized Services (SOR-SNPN-SI-LS) information from a second SNPN cell selected to avail the localized services in the TA, upon successful UE registration with the second SNPN cell. The SOR-SNPN-SI-LS information comprises entries indicating at least one GIN and at least one TAC of the TA included in location validity information corresponding to the at least one GIN. The method further comprises determining occurrence of a match based on the two conditions. The first condition corresponding to determining the match when, the at least one TAC included in the current TAI added to the forbidden list is associated with the at least one GIN indicated as an entry in the SOR-SNPN-SI-LS information. Further, the second condition corresponding to determining the match when the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list. Thereafter, the method comprises deleting the TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list, to avail the localized services in the TA from the second SNPN cell using the TA associated with the at least one TAC deleted from the forbidden list, upon determining occurrence of the match.

[0073] In a non-limiting embodiment of the disclosure, a UE for managing forbidden lists of Tracking Areas (TAs) in communication networks is disclosed. The UE comprises a processor and a memory communicatively coupled to the processor, where the memory stores processor executable instructions, which, on execution, may cause the UE to receive during the registration procedure, the MM reject cause message indicative of the failure in the UE registration with the first SNPN cell selected to avail the localized services in a TA. Further, the UE adds at least one GIN and a current Tracking Area Identity (TAI) comprising at least one TAC of the TA associated with the at least one GIN broadcasted by the first SNPN cell, to the forbidden list among the plurality of forbidden lists associated with the first SNPN cell, upon receiving the MM reject cause message. The UE further receives the SOR-SNPN-SI-LS information from the second SNPN cell selected to avail the localized services in the TA, upon the successful UE registration with the second SNPN cell. The SOR-SNPN-SI-LS information comprises entries indicating the at least one GIN and the at least one TAC of the TA included in location validity information corresponding to the at least one GIN. The UE further determines occurrence of a match based on the two conditions. The first condition corresponding to determining the match when, the at least one TAC included in the current TAI added to the forbidden list is associated with the at least one GIN indicated as an entry in the SOR-SNPN-SI-LS information. Further, the second condition corresponding to determining the match when the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list. Thereafter, the UE deletes the TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list, to avail the localized services in the TA from the second SNPN cell using the TA associated with the at least one TAC deleted from the forbidden list, upon determining occurrence of the match.

[0074] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

[0075] The present disclosure generally relates to the field of wireless communications, and more particularly to method and system for deleting Tracking Area Identity (TAI_ from forbidden TAI list based on Group ID for Network Selection (GIN).

[0076] 5G System (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 User Equipment (UE) is not allowed to operate for normal services (apart from emergency). The Mobile Station (MS) adds a Tracking Area (TA) to this list when it receives reject causes #12, #15 or #13 for example. If the UE is not operating in Standalone Non-Public Networks (SNPN) access operation mode, the UE 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 shall store a list of "5GS forbidden tracking areas for roaming":

[0077] - per SNPN; and

[0078] - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, per entry of the "list of subscriber data" or, if the UE supports access to an SNPN using credentials from a credentials holder, Public Land Mobile Network (PLMN) subscription.

[0079] The UE shall store a list of "5GS forbidden tracking areas for regional provision of service":

[0080] - per SNPN; and

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

[0082] In the present disclosure, these forbidden lists will further be referred to as 5GS_forbidden_TA_lists.

[0083] 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, IMS, etc.), or connectivity (e.g. 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 end user via a hosting network.

[0084] If the MS supports access to an SNPN providing access for localized services in SNPN, the SNPN selection parameters for access for localized services in SNPN, consisting of:

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

[0086] ii) a "credentials holder controlled prioritized list of preferred Group ID for Network Selection (GIN)s for access for localized services in SNPN", where each entry contains a GIN and a validity information consisting of time validity information.

[0087] In the present disclosure, i) and ii) will be referred to as CH_Lists and for simplicity ii) alone will be referred to as CH_List_GINs.

[0088] Provisioning information for SNPN selection by an MS supporting access to an SNPN providing access for localized services in SNPN consisting of:

[0089] a) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains:

[0090] 1) an SNPN identity;

[0091] 2) a validity information consisting of time validity information and optionally, location validity information; and

[0092] 3) optionally, location assistance information;

[0093] b) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains:

[0094] 1) a GIN;

[0095] 2) a validity information consisting of time validity information and optionally, location validity information; and

[0096] 3) optionally, location assistance information; or

[0097] c) both of the above.

[0098] The validity information consists of:

[0099] - 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

[0100] - Location validity information consisting of TA(s) or geo location.

[0101] Location assistance validity information consisting of:

[0102] -- Geolocation information, and / or,

[0103] -- Tracking Area information of serving networks, i.e. lists of TACs per PLMN ID or per PLMN ID and NID.

[0104] The time validity information contains one or more time periods. The location validity information contains one or more location information. If:

[0105] a) the location validity information is not available and at least one time period of the time validity information matches UE's current time; or

[0106] b) the location validity information is available, at least one time period of the time validity information matches UE's current time and at least one location information of the location validity information matches UE's current location;

[0107] then the validity information is met, otherwise the validity information is not met.

[0108] The GIN identifies a group of credential holders that are broadcasted by an SNPN cell. An SNPN-ID can be associated with one more GIN(s), as part of the broadcast information.

[0109] An SNPN selected for localized services in SNPN is an SNPN that is selected by an MS supporting access to an SNPN providing access for localized services in SNPN, when the access for localized services in SNPN is enabled, and the SNPN is selected according to:

[0110] a) subclause 4.9.3.1.1 bullet a0);

[0111] b) subclause 4.9.3.2.1 bullet a0); or

[0112] c) is manually selected by the user; and

[0113] i. the validity information of the SNPN is met;

[0114] ii. the validity information of GIN(s) broadcasted by the SNPN is met; or

[0115] iii. both

[0116] A UE operating in SNPN access operation mode only selects SNPNs. This includes the case when the UE is accessing an SNPN over 3GPP access, the case when the UE is accessing an SNPN over non-3GPP access and the case where the UE is accessing SNPN services via a PLMN.

[0117] A UE when it receives 5GMM _reject _causes like #12, #13, #15, but not limited to these 5GMM causes alone, adds a tracking area (TA) to the list of 5GS_forbidden_TA_lists. In the present disclosure, these causes may be referred to as 5GMM_reject _cause.

[0118] As per 3GPP TS 23.122, 23.501, 24.501, location validity information consists of tracking areas and / OR geo location information. The existing method may be further explained by consider the following scenario 1 as shown in Fig. 1.

[0119] 1) SNPN-1 is an SNPN selected for localized services in SNPN. The current SNPN-1 cell broadcasts GIN-1, GIN-2 and Tracking Area Code 1 (TAC-1) for example.

[0120] 2) UE triggers registration procedure gets rejected with 5GMM_reject _cause.

[0121] 3) UE adds TAC-1 to 5GS_forbidden_TA_lists for SNPN-1.

[0122] 4) UE selects SNPN-2 for example, which is an SNPN selected for localized services in SNPN, or a different tracking area of SNPN-1.

[0123] 5) Consider that the UE completes registration procedure.

[0124] 6) Now the UE receives SOR-SNPN-SI-LS information, with entries in "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN as:

[0125] a. GIN-2.

[0126] b. Time validity information;

[0127] c. Location validity information as TAC-1, TAC-3.

[0128] 7) TAC-1 for SNPN-1 remains in the 5GS_forbidden_TA_lists.

[0129] In the above scenario, the UE shall delete SNPN-1 + TAC-1 if identified by the credential holder controlled prioritized list of GINs from the list of 5GS_forbidden_TA_lists, as GIN-2 + TAC-1 is included in the SOR-SNPN-SI-LS information. But it is not clear how it is possible for the UE to identify and delete a TA from list of 5GS_forbidden_TA_lists based on GIN(s) entries in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN. Hence the issue at step 8 in the scenario. The problem is not limited to registration procedure, but any NAS procedure that can lead to NW sending 5GMM_reject _cause to the UE.

[0130] The present disclosure relates to a method and system for deleting TAI from forbidden Tracking Area Identity (TAI) list based on GIN. In an embodiment, if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5] subclause 3.9), the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

[0131] In an embodiment, if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP　TS　23.122　[5] subclause　3.9), the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

[0132] In another embodiment, the UE remembers that the UE had attempted in particular TAI of an SNPN because it was configured in the CH_lists and that the validity information was met. Later, when the UE receives SOR-SNPN-SI or SOR-SNPN-SI-LS optionally with non-empty "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" remove all such TAs which were added to 5GS_forbidden_TA_lists earlier.

[0133] In another embodiment Whenever NW sends the SOR-SNPN-SI-LS list to the UE, NW will ensure to include GIN(s) + SNPN(s) (SNPN(s) which broadcast the same GIN(s)) as part of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" in the SOR-SNPN-SI or SOR-SNPN-SI-LS information.

[0134] In an embodiment of the present disclosure, if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5] subclause 3.9), the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

[0135] In an embodiment of the present disclosure, if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5] subclause 3.9), the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

[0136] For example, considering the example scenario in the background, the UE shall add TAC-1 for SNPN-1 to 5GS_forbidden_TA_lists along with the broadcasted GIN(s) for SNPN-1, i.e. GIN-1 and GIN-2 on reception of 5GMM_reject _cause. Later, the UE receives SOR-SNPN-SI-LS from NW, with GIN-2, and TAC-1 and TAC-2 as location validity information. The UE can identify that TAC-1 + GIN-2 is in 5GS_forbidden_TA_lists for SNPN-1 and shall delete this TA from the 5GS_forbidden_TA_lists.

[0137] In an embodiment, there are two Scenarios in the present disclosure which are explained in scenario A, scenario B, and scenario C.

[0138] Scenario A:

[0139] 1) SNPN-1 is an SNPN selected for localized services in SNPN.

[0140] 2) The current SNPN-1 cell broadcasts GIN-1, GIN-2 and TAC-1 for example.

[0141] 3) UE triggers registration procedure gets rejected with 5GMM_reject _cause.

[0142] 4) UE adds TAC-1 to 5GS_forbidden_TA_lists for SNPN-1 along with GIN-1 & GIN-2.

[0143] 5) UE selects SNPN-2 for example, which is an SNPN selected for localized services in SNPN, or a different tracking area of SNPN-1.

[0144] 6) Consider that the UE completes registration procedure.

[0145] 7) Now, the UE receives SOR-SNPN-SI-LS information, with entries in "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN as:

[0146] d. GIN-2.

[0147] e. Time validity information,

[0148] f. Location validity information as TAC-1, TAC-3.

[0149] 8) TAC-1 for SNPN-1 along with GIN-2 is identified in the 5GS_forbidden_TA_lists & deleted from 5GS_forbidden_TA_lists.

[0150] In another embodiment, the UE remembers that the UE had attempted in particular TAI of an SNPN because it was configured in the CH_lists and that the validity information was met. The same is remember when a tracking area identity (TAI) is added to 5GS_forbidden_TA_lists on reception of 5GMM_reject_cause. Later when the UE receives SOR-SNPN-SI or SOR-SNPN-SI-LS optionally with non-empty "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" remove all such TAs which were added to 5GS_forbidden_TA_lists earlier.

[0151] For example, considering the example scenario 1, the UE shall add TAC-1 for SNPN-1 to 5GS_forbidden_TA_lists and remember that UE had camped in TAC-1 for SNPN-1 because TAC-1 for SNPN-1 was configured in one of the CH_lists and that the validity information was met. Later when the UE receives SOR-SNPN-SI or SOR-SNPN-SI-LS optionally with non-empty "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" remove SNPN-1 + TAC-1 and all similar TA s from 5GS_forbidden_TA_lists.

[0152] Scenario B:

[0153] 1) SNPN-1 is an SNPN selected for localized services in SNPN.

[0154] 2) The current SNPN-1 cell broadcasts GIN-1, GIN-2 and TAC-1 for example.

[0155] 3) UE triggers registration procedure gets rejected with 5GMM_reject _cause.

[0156] 4) UE adds TAC-1 to 5GS_forbidden_TA_lists for SNPN-1 along with GIN-1 & GIN-2 & remembers that the UE had attempted in TAC-1 of SNPN-1 because it was configured in the CH_lists and that the validity information was met.

[0157] 5) UE selects SNPN-2 for example, which is an SNPN selected for localized services in SNPN, or a different tracking area of SNPN-1.

[0158] 6) Consider that the UE completes registration procedure.

[0159] 7) Now UE receives SOR-SNPN-SI-LS information, with valid entries in "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN.

[0160] 8) TAC-1 for SNPN-1 is deleted from 5GS_forbidden_TA_lists.

[0161] In another embodiment of the present disclosure, whenever the network sends the SOR-SNPN-SI-LS list to the UE, the network ensures to include GIN + SNPN(s) (SNPN(s) which broadcast the same GIN(s)) as part of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN". This means:

[0162] a. The UE can access an SNPN if the broadcasted GIN / GIN(s) of the SNPN and the SNPN-ID of the SNPN is part of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN". And the validity information is met. i.e. say "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" has SNPN-1 + GIN-1 only, then UE can access SNPN-1 if it broadcast GIN-1. If there is another SNPN say SNPN-2 broadcasting GIN-1, the UE cannot access SNPN-2.

[0163] b. This SNPN-ID + GIN-ID combination may be used by the UE to save any tracking area in the 5GS_forbidden_TA_lists as explained in solution 1.

[0164] c. The SNPN-ID + GIN-ID combination received in "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" may be used to remove corresponding TAC + SNPN-ID + GIN-ID from 5GS_forbidden_TA_lists on reception of SOR-SNPN-SI-LS. i.e. if SNPN-1 + GIN-1 & SNPN-2 + GIN-1 are present in, and say the network sends SOR-SNPN-SI or SOR-SNPN-SI-LS with "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" entry that has SNPN-1 + GIN-1 & SNPN-2 + GIN-2, the UE may remove SNPN-1 + GIN-1 combination from 5GS_forbidden_TA _lists.

[0165] In the present disclosure, for simplicity "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN” is to be referred to as CH_List_GINs.

[0166] Scenario C:

[0167] 1) SNPN-1 broadcasts GIN-1, TAC-1 &SNPN-1 + GIN-1 is configured in CH_list_GINs.

[0168] 2) Registration Request in SNPN-1.

[0169] 3) Registration Reject with cause 5GMM_reject_cause.

[0170] 4) UE adds SNPN-1 + TAC-1 + GIN-1 to 5GS_forbidden_TA _lists.

[0171] 5) UE later registers in SNPN-2.

[0172] 6) UE receives SOR-SNPN-SI or SOR-SNPN-SI-LS information with empty CH_list_GINs:

[0173] a. GIN-1 + SNPN-1, validity information TAC-1,

[0174] b. GIN-2 + SNPN-2.

[0175] 7) UE removes SNPN-1 + TAC-1 + GIN-1 from 5GS_forbidden_TA_lists based on entries in CH_list_GINs from step 5.

[0176] The scenaarios proposed in the present disclosure is a method and system for deleting TAI from forbidden Tracking Area Identity (TAI) list based on GIN.

[0177] The table below includes a list of abbreviations and acronyms that are being used in the description of the present disclosure:

[0178]

[0179] Disclosed herein is a method and a system for managing forbidden lists of Tracking Areas (TAs) in communication networks. According to existing techniques, UE has no mechanism to identify TACs using broadcasted GIN. This is because, when a TAC is added to forbidden lists, the broadcasted GIN of that SNPN is lost, and the UE does not remember the GIN broadcasted by the SNPN. Hence the associated GIN value of the TAC in the forbidden lists is also lost.

[0180] To solve the above problem, the present disclosure discloses a method and a system for managing forbidden lists of Tracking Areas (TAs) in communication networks. In the present disclosure, system may refer to a User Equipment (UE) capable of interacting in a manner that the method of the present disclosure is implemented. In some embodiments, the UE may also be referred to as an apparatus or device in the context of the present disclosure. The present disclosure provides adding by the UE, a current Tracking Area Identity (TAI) comprising TACs corresponding to an SNPN, to forbidden list of TA, along with the GINs broadcasted by the SNPN. This gives the UE a mechanism to identify the TACs in the forbidden list of TAs, based on the associated GIN broadcasted by the SNPN. Later when the UE receives the location validity information from another SNPN, the UE identifies the TACs based on the associated GIN broadcasted by the SNPN. Thereafter, the UE deletes the TAs identified by the corresponding GINs included in the location validity information, from the forbidden list of TA.

[0181] In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0182] Fig. 1shows an exemplary environment for managing forbidden lists of Tracking Areas (TAs) in communication networks, in accordance with some embodiments of the present disclosure.

[0183] Fig.1 shows an environment 100 for managing forbidden lists of Tracking Areas (TAs). As shown, the environment 100 includes a User Equipment 102, Access and Management Mobility Function (AMF) 106, and a plurality of Stand-alone Private Network (SNPN) cells 104 (a SNPN cell 1041, a SNPN cell 1042, ...................and a SNPN 104N, collectively referred as the plurality of SNPN cells 104). A person skilled in art may understand that for illustration purposes only three SNPNs are shown in Fig. 1. As seen, the UE 102 is in communication with the AMF 106 which is associated with the plurality of SNPN cells 104. The SNPN refers to a private cellular network which offers communication services such as localized services to enterprises, factories, or other organizations for their own private use cases.

[0184] The SNPN includes various components, such as, but not limited to, gNodeBs (base stations) and 5G Core network elements, and the like. These components enable wireless communication services, such as, but not limited to, voice, messaging, and data transfer, to the UEs within a specific geographical area. The AMF 106 corresponds to a core network function which is responsible for handling the UE's connection and data session management. The network function is defined as a specialized component within a communication network responsible for performing specific tasks, such as routing, switching, security, load balancing, quality of service management, or Network Address Translation (NAT). These network functions are fundamental to the operation and efficiency of modern communication networks, enabling seamless processing, management, and forwarding of data packets to support diverse communication services and ensure optimal network performance. Notably, the AMF 106 is a network function which is responsible for managing connection, user access and mobility tasks within the communication network. For example, the AMF 106 may handle procedures related to initial access, mobility management, and session management for user devices, ensuring seamless connectivity and efficient service delivery in the communication network.

[0185] In an embodiment, when the UE 102 supports access to an SNPN from the plurality of SNPN cells 104 for localized services, the UE 102 maintains lists corresponding to "temporarily forbidden SNPNs for access for localized services in SNPN" and "permanently forbidden SNPNs for access for localized services in SNPN". If UE 102 supports access to an SNPN for localized services, then for automatic SNPN selection, the UE 102 cannot select an SNPN which is in either of these lists.

[0186] The localized services correspond to services which are provided by one of the plurality of SNPN cells 104 in limited geographical areas, and for limited time durations. For example, live broadcast of an ongoing music concert or football game to viewers within area of the stadium, and only during the duration of the concert or the game can be considered as a localized service. The UE 102 is usually enabled either manually or through applications for accessing the localized services in one of the plurality of SNPN cells 104. For the UE 102 to be able to identify, discover and access such SNPNs, home operator configures a list of such SNPN (networks) which provide localized services, in the UE through several mechanisms. Such a list contains a list of such SNPNs, and time and location validity of every SNPN of the plurality of SNPN cells 104, i.e. the geographical location corresponding to the time validity information and time duration of the day corresponding to location validity information, when such an SNPN is accessible. Therefore, the UE 102 which is enabled for localized services, is configured to search and camp in such SNPNs, only in those specific geographical areas, and within the specific time duration of the day. For example, if the time validity information of SNPN 1041indicates, time validity from 2pm to 3pm of the day, and the location validity information indicates the geographical location X on earth, then the UE 102 can access SNPN 1041only at location X, during 2pm to 3pm of the day.

[0187] The UE 102 enables efficient management of forbidden lists of TAs in the communication network. The UE 102 may include, but not limited to, a laptop computer, a desktop computer, a Personal Computer (PC), a notebook, a smartphone, a tablet, a server, a network server, a cloud-based server, and the like. In an embodiment, the UE 102 may be implemented as a hand-held mobile communication device akin to a mobile phone.

[0188] The UE 102 may include a I / O interface 108, a memory 110, and a processor 112. In some embodiments, the memory 110 may be communicatively coupled to the processor 112. The memory 110 stores instructions, executable by the processor 112, which, on execution, may cause the UE 102 to manage managing forbidden lists of Tracking Areas (TAs) in communication networks, as disclosed in the present disclosure.

[0189] Herein, UE's 102 subscription may allow UE 102 to access the plurality of SNPN cells 104, and a first SNPN cell 1041(hereafter referred as SNPN-1) may be selected from the plurality of SNPN cells 104, as the SNPN-1 corresponds to a preferred network for the required localized service. In an embodiment, each SNPN of the plurality of SNPNs are configured to access a plurality of TAs. Therefore, a plurality of Tracking Area Code (TAC) may be valid for each SNPN of the plurality of SNPN. Accordingly, the SNPN-1 may broadcast at least one Group ID for Network (GIN) such as GIN-1, GIN-2 and at least one TAC of the TA associated with the at least one GIN such as TAC-1. The SNPN-1 sends the broadcasted information to the UE 102 through the AMF 106. However, during a registration procedure initiated by the UE 102 post broadcasting, a reject cause message such as a 5GMM reject cause message may be received by the UE 102 from the AMF 106. The 5GMM reject cause message may be received when the registration procedure initiated by the UE 102 may not be accepted by the communication network.

[0190] Thereafter, the UE 102 may add the current TAI comprising the TAC-1 to a forbidden list such as 5GS_forbidden_TA_list for SNPN-1, along with GIN-1 and GIN-2. In an embodiment, adding the at least one GIN and the current TAI comprising the at least one TAC associated with the at least one GIN to the forbidden list comprises storing the GIN-1, GIN-2 and the TAC-1 associated with the GIN-1 which are broadcasted by the SNPN-1 in one of the plurality of forbidden lists. The plurality of forbidden lists comprise "5GS forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for roaming", and “forbidden tracking area list corresponding to other Radio Access Technologies (RATs)”, for the SNPN-1, and a selected entry of "list of subscriber data" or a selected Public Land Mobile Network (PLMN) subscription. The PLMN subscription is referred as a set of data and credentials that UE 102 or its subscriber utilize for accessing a specific PLMN.

[0191] Further, the UE 102 may select a second SNPN cell 1042(hereafter referred as SNPN-2) for availing the localized services and initiate the registration procedure with the SNPN-2. In an embodiment, upon successful UE registration with the SNPN-2, the UE 102 may receive Steering of Roaming SNPN Selection Information for Localized Services (SOR-SNPN-SI-LS) information from the SNPN-2. The SOR-SNPN-SI-LS information comprises entries in “credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN”. The entries in the SOR-SNPN-SI-LS information indicate at least one GIN, at least one TAC of the TA included in location validity information corresponding to the at least one GIN and time validity information. For example, consider the at least one GIN and the at least one TAC received as entries of the SOR-SNPN-SI-LS information correspond to GIN-2 and TAC-1, TAC-3, respectively.

[0192] Furthermore, the UE 102 may be further configured to determine occurrence of a match between the entries received in the SOR-SNPN-SI-LS information and information in the forbidden list. The occurrence of the match is determined when the at least one TAC in the current TAI added to the forbidden list is associated with the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information, and when the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list.

[0193] Thereafter, the UE 102 is configured to delete the TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list, to avail the localized services in the TA from the second SNPN cell using the at least one TAC deleted from the forbidden list, upon determining occurrence of the match. Particularly, the UE 102 is configured to delete the TA associated with the at least one TACs included in the location validity information corresponding to the at least one GINs which is identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with the previous SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if the tracking area(s) in these lists is associated with the same GIN. For example, consider the TA associated with the at least one TAC corresponds to TAC-1 in the location validity information and in the forbidden list. Further consider the at least one GIN corresponding to the TAC-1 is GIN-2. In this example, the occurrence of the match is determined, and the TAC-1 may be considered for deletion by the UE 102 from the forbidden list. Therefore, the TA associated with the TAC-1 may be utilized by the UE 102 to avail the localized services from the SNPN-2.

[0194] Therefore, the present disclosure facilitates handling and identifying TACs in present in the forbidden TA lists for a given SNPN cell, based on the location validity information corresponding to the GIN and which is also received in the SOR-SNPN-SI-LS information from another SNPN cell. Particularly, based on the present disclosure, the UE 102 is able to delete the TA associated with the TAC from the forbidden lists of the TAs, if the same TACs have been indicated in the location validity information, along with the same corresponding GIN. In this manner, the TAs may be utilized by other SNPN cells for availing localized services.

[0195] Fig. 2shows a detailed block diagram of a UE in a communication network, in accordance with some embodiments of the present disclosure.

[0196] Fig. 2shows internal architecture of the UE in accordance with some embodiments of the present disclosure. The UE 102 may include at least one Central Processing Unit (“CPU” or “processor”) 112 and a memory 110storing instructions executable by the at least one processor 112. The processor 112 may comprise at least one data processor for executing program components for executing user or system-generated requests. The memory 110 is communicatively coupled to the processor 112. The UE 102 further comprises an Input / Output (I / O) interface 108. The I / O interface 108 is coupled with the processor 112through which an input signal or / and an output signal is communicated.

[0197] In some implementations, the UE 102 may include data 200 and modules 202. As an example, the data 200 may be stored within the memory 110 associated with the UE 102. In some embodiments, data 200 may include, for example, registration data 204, forbidden data 206, match determination data 208, deleted data 210 and other data 212. In some embodiments, the data 200 may be stored in the memory 110 in form of various data structures.

[0198] The registration data 204 comprises information related to status of registration which may correspond to one of, a successful UE registration and a failure in UE registration. In an embodiment, the registration data 204 may be associated with the registration of the UE with at least one of the plurality of SNPN cells.

[0199] The forbidden data 206 comprises entries of current TAI comprising at least one TAC, and at least one GIN being added to the plurality of forbidden lists associated with the UE 102. In an embodiment, the plurality of forbidden lists comprises lists corresponding to "5GS forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for roaming", and “forbidden tracking area list corresponding to other Radio Access Technologies (RATs)”.

[0200] The match determination data 208 comprises the two conditions based on which the match between the entries received in the SOR-SNPN-SI-LS information and the information in the forbidden list is determined. Particularly, the first condition corresponds to when the at least one TAC in the current TAI added to the forbidden list is associated with the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information. Further, the second condition corresponds to when the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list. In an embodiment, the match determination data 208 may comprise the determined results corresponding to one of, the occurrence of match or failure in occurrence of match.

[0201] The deleted data 210 comprises the entries of the TAs associated with the at least one TAC which are deleted from the forbidden lists and are further utilized for availing localized services.

[0202] The other data 212 may be stored data, including temporary data and temporary files, generated by the modules 202 for performing the various functions of the UE 102.

[0203] In an embodiment, the data 200 in the memory 110 are processed by the one or more modules 202 present within the memory 110 of the UE 102.

[0204] One or more modules 202 along with the data 200, functions to manage forbidden lists of Tracking Areas (TAs) in communication networks. In one implementation, the one or more modules 202 may include, but are not limited to, a receiving module 214, an adding module 216, a determining module 218, a deleting module 220 and one or more other modules 222.

[0205] In an embodiment, the one or more modules 202 may be implemented as dedicated units. As used herein, the term module refers to an application specific integrated circuit (ASIC), an electronic circuit, a field-programmable gate arrays (FPGA),Programmable System-on-Chip　 (PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In some implementations, the one or more modules 202 may be communicatively coupled to the processor 112 for performing one or more functions of the UE 102. The said modules 202 when configured with the functionality defined in the present disclosure will result in a novel hardware.

[0206] In an embodiment, during the registration procedure, the receiving module 214 may receive the MM reject cause message indicative of the failure in UE registration with the first SNPN cell selected to avail localized services in the TA. For example, the reject cause may correspond to one of the reject causes #12, #15 or #13, as defined in the specification for the Non-Access-Stratum (NAS) protocol for the Evolved Packet System (EPS) in LTE. In an embodiment, prior to receiving the MM reject cause message, the receiving module 214 may receive broadcasted information comprising the identifier of the first SNPN cell, the at least one GIN, and the at least one TAC associated with the at least one GIN.Fig. 3shows step 1 where the UE 102 has selected SNPN-1 from the plurality of SNPN cells. In an embodiment, the plurality of SNPN cells are identified by the GIN corresponding to GIN-1, which is part of a list corresponding to “Credentials Holder controlled prioritized list of GINs”. The selection of SNPN-1 allows the UE 102 to access the localized services provided by that specific network. Thereafter, as seen from Fig. 3, the SNPN-1 broadcasts GIN-1, GIN-2 and TAC-1 which is received as the broadcasted information by the UE 102. Further, at step 3 the UE 102 receives the MM reject cause message post sending registration request to SNPN-1. The information related to the registration status and the broadcasted information is stored in the registration data 204 which is sent by the receiving module 214 to the adding module 216.

[0207] In an embodiment, the adding module 216 may be configured to receive the registration data 204 comprising the registration status from the receiving module 214. Thereafter, adding module 216 is configured to add the at least one Group ID for Network (GIN) and the current TAI comprising the at least one Tracking Area Code (TAC) of the TA associated with the at least one GIN which are broadcasted by the first SNPN cell, to the forbidden list among the plurality of forbidden lists associated with the first SNPN cell. The adding module 216 is configured to perform the addition to the forbidden list upon receiving the MM reject cause message, which is identified based on the information stored in the registration data 204. The adding module 216 may be configured to add the at least one GIN and the current TAI comprising the at least one TAC associated with the at least one GIN to the forbidden list by storing the at least one GIN and the at least one TAC associated with the at least one GIN broadcasted by the first SNPN cell in one of the plurality of forbidden lists. For example, if the SNPN is an SNPN selected for localized services in SNPN, the UE 102 shall store the current TAC in the list of “5GS forbidden tracking areas for regional provision of service” or “5GS forbidden tracking areas for roaming” for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN, if any.Fig. 3shows step 4 where the UE 102 adds TAI comprising the TAC-1 to the forbidden list corresponding to “5GS_forbidden_TA_lists” for SNPN-1, along with GIN-1 & GIN-2, on reception of 5GMM_reject_cause. In an embodiment, the forbidden lists may be stored in forbidden data 206 and may be sent to the determining module 218 by the adding module 216.

[0208] In an embodiment, the receiving module 214 may be configured to receive the SOR-SNPN-SI-LS information from the second SNPN cell selected to avail the localized services in the TA. The SOR-SNPN-SI-LS information is received upon successful UE registration with the second SNPN cell. The SOR-SNPN-SI-LS information comprises entries indicating the at least one GIN and the at least one TAC of the TA included in the location validity information corresponding to the at least one GIN. Particularly, the SOR-SNPN-SI-LS information comprises the entries in “credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN”. The receiving module 214 may be configured to receive the SOR-SNPN-SI-LS information upon selecting SNPN-2 as an SNPN selected for localized services in SNPN, or for a different tracking area of SNPN-1. Upon selecting the SNPN-2, the UE 102 may successfully complete registration procedure with the SNPN-2.Fig. 3shows steps 5 and 6 indicating the selection and successful completion of registration of UE 102 with SNPN-2. Step 7 shows that the SOR-SNPN-SI information comprises entries in the “credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN”. The entries correspond to, GIN-2, time validity information, and location validity information as TAC-1, TAC-3. In an embodiment, the registration status with respect to SNPN-2 is stored in the registration data and the SOR-SNPN-SI-LS information may be stored in other data 212 which may be sent by the receiving module 214 to the determining module 218.

[0209] In an embodiment, the determining module 218 may be configured to receive the forbidden data 206 from the adding module 216 and further receive the SOR-SNPN-SI information in the other data 212 from the receiving module 214. Thereafter, the determining module 218 may be configured to determine the occurrence of the match between the entries received in the SOR-SNPN-SI-LS information and the information in the forbidden list. The determining module 218 may determine the match based on the two conditions store in the match determination data 208. Particularly, when both the conditions are satisfied, the occurrence of match is determined by the determining module 218. In an embodiment, when the first condition is not satisfied, the determining module 218 may determine a failure in occurrence of match, leading to selection of another SNPN different from SNPN-1 and SNPN-2. In an embodiment, the determined results comprising one of, the match in occurrence or the failure in occurrence, may be stored in the match determination data 208 which are sent to the deleting module 220 by the determining module 218.Fig. 3shows step 8 indicating the identification TAC-1 for SNPN-1 along with GIN-2 in the 5GS_forbidden_TA_lists.

[0210] In an embodiment, the deleting module 220 may be configured to receive the match determination data 208 from the determining module 218. Thereafter, the deleting module 220 is configured to delete the TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list. The deleting module 220 is configured to delete the TA associated with the at least one TAC from the forbidden list to avail the localized services in the TA from the second SNPN cell, based on the determined results stored in the match determination data 208. Particularly, the deleting module 220 is configured to delete the TA associated with the TACs included in the location validity information corresponding to a GIN which is identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with an SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if the TACs in these lists are associated with the same GIN.Fig. 3shows step 8 indicating the deletion of the TAC-1 from the 5GS_forbidden_TA_lists as the determined results correspond to occurrence of match.

[0211] Fig. 4is a flowchart illustrating a method for a UE for managing forbidden lists of Tracking Areas (TAs) in communication networks, in accordance with some embodiments of the present disclosure.

[0212] As illustrated inFig. 4, the method 400 comprises one or more blocks illustrating a method of UE for managing forbidden lists of Tracking Areas (TAs) in communication networks, in accordance with some embodiments of the present disclosure. The method 400 may be described in the general context of computer-executable instructions. Generally, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform functions or implement abstract data types.

[0213] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 400. Additionally, individual blocks may be deleted from the methods without departing from scope of the subject matter described herein. Furthermore, the method 400 can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0214] At block 402, the method 400 may include receiving, by the UE 102, during the registration procedure, the MM reject cause message indicative of the failure in the UE registration with the first SNPN cell selected to avail the localized services in a TA. In an embodiment, prior to receiving the MM reject cause message, broadcasted information is received which comprises the identifier of the first SNPN cell, the at least one GIN, and the at least one TAC associated with the at least one GIN.

[0215] At block 404, the method 400 may include adding, by the UE 102, at least one GIN and a current TAI comprising the at least one TAC of the TA associated with the at least one GIN broadcasted by the first SNPN cell, to the forbidden list among the plurality of forbidden lists associated with the first SNPN cell, upon receiving the MM reject cause message. In an embodiment, adding the at least one GIN and the at least one TAC associated with the at least one GIN to the forbidden list comprises storing the at least one GIN and current TAI comprising the at least one TAC associated with the at least one GIN broadcasted by the first SNPN cell in one of the plurality of forbidden lists comprising "5GS forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for roaming", and “forbidden tracking area list corresponding to other Radio Access Technologies (RATs)”, for the first SNPN cell, and a selected entry of "list of subscriber data" or a selected PLMN subscription.

[0216] At block 406, the method 400 may include receiving, by the UE 102, the SOR-SNPN-SI-LS information from the second SNPN cell selected to avail the localized services in the TA, upon the successful UE registration with the second SNPN cell. In an embodiment, the SOR-SNPN-SI-LS information comprises entries indicating the at least one GIN and the at least one TAC of the TA included in location validity information corresponding to the at least one GIN. In an embodiment, the entries are included in “credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN”.

[0217] At block 408, the method 400 may include determining, by the UE 102, occurrence of a match based on the two conditions. The first condition corresponding to determining the match when, the at least one TAC included in the current TAI added to the forbidden list is associated with the at least one GIN indicated as an entry in the SOR-SNPN-SI-LS information. Further, the first condition corresponding to determining the match when the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list.

[0218] At block 410, the method 400 may include deleting, by the UE 102, the TA associated with the at least one TAC of the TA included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list, to avail the localized services in the TA from the second SNPN cell using the TA deleted from the forbidden list, upon determining occurrence of the match. In an embodiment, deleting the at least one TAC comprises deleting the TA associated with the at least one TAC of the TAs included in the location validity information corresponding to the at least one GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the forbidden list associated with the first SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, when the at least one TAC of the TAs in the forbidden list is associated with the at least one GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN".

[0219] Fig. 5is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.

[0220] In some embodiments, FIG. 5 illustrates a block diagram of an exemplary computer system 500 for implementing embodiments consistent with the present disclosure. In some embodiments, the computer system 500 can be the UE 102 that comprises a processor (also referred as a processor 502 in this FIG. 5) that is used for managing forbidden lists of Tracking Areas (TAs) in communication networks. The processor 502 may include at least one data processor for executing program components for executing user or system-generated business processes. The processor 502 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

[0221] The processor 502 may be disposed in communication with input devices 510 and output devices 511 via I / O interface 501. The I / O interface 501 may employ communication protocols / methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE), WiMax, or the like), etc.

[0222] Using the I / O interface 501, computer system 500 may communicate with input devices 510 and output devices 511.

[0223] In some embodiments, the processor 502 may be disposed in communication with a communication network 509 via a network interface 503. The network interface 503 may communicate with the communication network 509. The network interface 503 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc. Using the network interface 503 and the communication network 509, the computer system 500 may communicate with the plurality of SNPN cells 104 via the AMF 106.

[0224] The communication network 509 can be implemented as one of the different types of networks, such as intranet or Local Area Network (LAN) and such within the organization. The communication network 509 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), etc., to communicate with each other.

[0225] Further, the communication network 509 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc. In some embodiments, the processor 502 may be disposed in communication with a memory 505 (e.g., RAM, ROM, etc. not shown in FIG. 5) via a storage interface 504. The storage interface 504 may connect to memory 505 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fibre channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.

[0226] The memory 505 may store a collection of program or database components, including, without limitation, a user interface 506, an operating system 507, a web browser 508 etc. In some embodiments, the computer system　500 may store user / application data, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.

[0227] Operating system　507　may facilitate resource management and operation of computer system　500. Examples of operating systems include, without limitation, APPLE®MACINTOSH®OS X®, UNIX®, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTION®(BSD), FREEBSD®, NETBSD®, OPENBSD, etc.), LINUX®DISTRIBUTIONS (E.G., RED HAT®, UBUNTU®, KUBUNTU®, etc.), IBM®OS / 2®, MICROSOFT®WINDOWS®(XP®, VISTA® / 7 / 8, 10 etc.), APPLE®IOS®, GOOGLETMANDROIDTM, BLACKBERRY®OS, or the like. User interface　506　may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to computer system　500, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, Apple®Macintosh®operating systems' Aqua®, IBM®OS / 2®, Microsoft®Windows®(e.g., Aero, Metro, etc.), web interface libraries (e.g., ActiveX®, Java®,　Javascript®, AJAX, HTML, Adobe®Flash®, etc.), or the like.

[0228] The computer system　500　may implement web browser　508　stored program components. Web browser　508　may be a hypertext viewing application, such as MICROSOFT®INTERNET EXPLORER®, GOOGLETMCHROMETM, MOZILLA®FIREFOX®, APPLE®SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers 508 may utilize facilities such as AJAX, DHTML, ADOBE®FLASH®, JAVASCRIPT®, JAVA®, Application Programming Interfaces (APIs), etc. The computer system 500　may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ACTIVEX®, ANSI®C++ / C#, MICROSOFT®,. NET, CGI SCRIPTS, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT®exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system 500 may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLE®MAIL, MICROSOFT®ENTOURAGE®, MICROSOFT®OUTLOOK®, MOZILLA®THUNDERBIRD®, etc.

[0229] FIG. 6 is a block diagram of a terminal or user equipment (UE) 600 according to an embodiment of the disclosure.

[0230] The terminal is an electronic device capable of wireless communication, may include a User Equipment (UE), a portable phone, a smartphone, a tablet, an Internet of things (IoT) device, etc., having various form factors, and may perform wireless communication with a base station (BS) through a wireless channel.

[0231] Referring to FIG. 6, the UE 600 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 601, at least one processor (hereinafter, referred to as simply “processor”) 602, and at least one memory (hereinafter, referred to as simply “memory”) 603. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 601, the processor 602, and the memory 603 of the UE 600 may operate. However, components of the UE 600 are not limited to the exemplary components illustrated in FIG. 6. In another embodiment, the UE 600 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 601, the processor 602, or the memory 603 may be integrated in the form of one component. Furthermore, the UE of FIG. 6 corresponds to the UE of the FIG. 1 and FIG. 2.

[0232] The transceiver 601 may be a communication circuit or communication circuitry that enables the UE 600 to perform wireless communication with a node or an entity of a network. For example, the transceiver 601 may enable the UE 600 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 601 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (601) may include all subsequent generations of evolved wireless communications.

[0233] According to an embodiment, the UE 600 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) sual connectivity (EN-DC), the UE 600 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 600 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 600 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0234] According to an embodiment, the transceiver 601 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 601 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 601 may output a signal received through a wireless channel to the processor 602 and may transmit, through a wireless channel, a signal output from the processor 602.

[0235] The processor 602 may control general operations of the UE 600 according to embodiments of the disclosure. The processor 602 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 602 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 603, individually, collectively or in any combination thereof. Further, the processor 602 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0236] The processor 602 may be electrically, operatively, or communicatively coupled to the transceiver 601 to control the transceiver 601.

[0237] The processor 602 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 602 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer) . In a specific embodiment, at least a part of the processor 602 may be included in one chip and the other part of the processor 602 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 601 or the memory 603.

[0238] The processor 602 may perform or control or cause an operation of the UE 600 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 602 may control operations of the UE 600 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 602 may execute a computer program, codes, or instructions stored in the memory 603, so as to control other components of the UE 600 to enable execution of various operations.

[0239] The memory 603 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 603 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0240] The memory 603 may be electrically, operatively, or communicatively coupled to the processor 602 and may be accessed by the processor 602.

[0241] The memory 603 may store a computer program, codes, or instructions executable by the processor 602. According to an embodiment, a computer program, codes, or instructions executable by the processor 602 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 603, the processor 602 may perform various functions according to an embodiment of the disclosure.

[0242] According to an embodiment of the disclosure, operations of the UE 600 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 603 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0243] FIG. 7 is a block diagram of a base station (BS) 700 according to an embodiment of the disclosure.

[0244] The BS 700 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 700 through a wireless channel.

[0245] Referring to FIG. 7, the BS 700 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 701, at least one processor (hereinafter, referred to as simply “processor”) 702, and at least one memory (hereinafter, referred to as simply “memory”) 703. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 701, the processor 702, and the memory 703 of the BS 700 may operate. However, components of the BS 700 are not limited to the exemplary components illustrated in FIG. 7. In another embodiment, the BS 700 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 701, the processor 702, or the memory 703 may be integrated in the form of one component.

[0246] The transceiver 701 may be a communication circuit or communication circuitry that enables the BS 700 to perform wireless communication with a node or an entity of a network. For example, the transceiver 701 may enable the BS 700 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 701 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (701) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 701 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 701 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 701 may output a signal received through a wireless channel to the processor 702 and may transmit, through a wireless channel, a signal output from the processor 702.

[0247] Meanwhile, according to an embodiment of the present disclosure, the BS 700 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 700 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 7, when the BS 700 performs wired communication, the BS 700 may further include a separate network interface for wired communication in addition to the transceiver 701. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0248] The processor 702 may control general operations of the BS 700 according to embodiments of the disclosure. The processor 702 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 702 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 703, individually, collectively or in any combination thereof. Further, the processor 702 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0249] The processor 702 may be electrically, operatively, or communicatively coupled to the transceiver 701 to control the transceiver 701.

[0250] The processor 702 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 702 may be included in one chip and the other part of the processor 702 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 701 or the memory 703.

[0251] The processor 702 may perform or control or cause an operation of the BS 700 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 702 may control operations of the BS 700 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 700 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 702 may execute a computer program, codes, or instructions stored in the memory 703, so as to control other components of the BS 700 to enable execution of various operations.

[0252] The memory 703 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 703 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0253] The memory 703 may be electrically, operatively, or communicatively coupled to the processor 702 and may be accessed by the processor 702.

[0254] The memory 703 may store a computer program, codes, or instructions executable by the processor 702. According to an embodiment, a computer program, codes, or instructions executable by the processor 702 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 703, the processor 702 may perform various functions according to an embodiment of the disclosure.

[0255] According to an embodiment of the disclosure, operations of the BS 700 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 703 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0256] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with network entity such as an Access and Mobility Management Function (AMF) or a Session Management Function (SMF) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0257] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0258] FIG. 8 is a block diagram of a network entity 800 according to an embodiment of the disclosure.

[0259] The network entity 800 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 800. Furthermore, the network entity 800 of FIG. 8 corresponds to the AMF entity of the FIG. 1.

[0260] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0261] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0262] Referring to FIG. 8, the network entity 800 may include at least one network interface 801, at least one processor 802 (hereinafter, “processor”), and at least one memory 803 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 800, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 8. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0263] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 801, the processor 802, and the memory 803 of the network entity 800 may operate. However, components of the network entity 800 are not limited to the exemplary components illustrated in FIG. 8. In another embodiment, the network entity 800 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 801, the processor 802, or the memory 803 may be integrated in the form of one component.

[0264] The network interface 801 is a collective term for a transmitter part of the network entity 800 and a receiver part of the network entity 800, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 801 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 801 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 801 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0265] The processor 802 may control general operations of the network entity 800 according to embodiments of the disclosure. The processor 802 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 802 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 803, individually, collectively or in any combination thereof. Further, the processor 802 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0266] According to an embodiment, the processor 802 may be electrically, operatively, or communicatively coupled to the network interface 801 to control the network interface 801.

[0267] The processor 802 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 802 may be included in one chip and the other part of the processor 802 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the network interface 801 or the memory 803.

[0268] The processor 802 may perform or control or cause an operation of the network entity 800 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 802 may control operations of the network entity 800 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 802 may execute a computer program, codes, or instructions stored in the memory 803, so as to control other components of the network entity 800 to enable execution of various operations.

[0269] The memory 803 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 803 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0270] The memory 803 may be electrically, operatively, or communicatively coupled to the processor 802 and may be accessed by the processor 802.

[0271] The memory 803 may store a computer program, codes, or instructions executable by the processor 802. According to an embodiment, a computer program, codes, or instructions executable by the processor 802 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 803, the processor 802 may perform various functions according to an embodiment of the disclosure.

[0272] According to an embodiment of the disclosure, operations of the network entity 800 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 803 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0273] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

[0274] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.

[0275] An embodiment of the present disclosure the present disclosure provides a method and a system for managing forbidden lists of Tracking Areas (TAs) in communication networks. The present disclosure provides adding by the UE a current TAI comprising the TACs corresponding to an SNPN, to forbidden list of TA, along with the GINs broadcasted by the SNPN. This gives the UE a mechanism to identify the TACs in the forbidden list of TAs, based on the associated GIN broadcasted by the SNPN as the UE remembers the GIN broadcasted by the SNPN. Therefore, when the UE receives the location validity information from another SNPN, the UE is capable of identifying the TACs based on the associated GIN broadcasted by the SNPN, as the TACs are saved in association with the GINs, thereby avoiding the UE from losing the GIN value of the TACs. Thereafter, the UE deletes the TA associated with the TACs identified by the corresponding GINs included in the location validity information, from the forbidden list of TA. In this manner, the TAs which were previously in the forbidden lists may be utilized by other SNPN cells for availing localized services.

[0276] According to an embodiment of the present disclosure, a method includes receiving MM reject cause message indicative of failure in UE registration with first SNPN cell selected to avail localized services in TA. Followed by adding at least one GIN and current TAI comprising at least one TAC of TA associated with at least one GIN broadcasted by first SNPN cell, to forbidden list associated with first SNPN cell. Further, receiving SOR-SNPN-SI-LS information from second SNPN cell selected to avail localized services in TA. The SOR-SNPN-SI-LS information comprises entries indicating at least one GIN and at least one TAC of TA included in location validity information corresponding to at least one GIN. Thereafter determining occurrence of match based on two conditions. Thereafter, deleting TA associated with at least one TAC included in location validity information corresponding to at least one GIN received as entry of SOR-SNPN-SI-LS information, from forbidden list upon determining occurrence of match.

[0277] According to an embodiment of the present disclosure, a method of managing forbidden lists of Tracking Areas (TAs) in communication networks comprising: receiving, by a User Equipment (UE), during a registration procedure, a Mobility Management (MM) reject cause message indicative of a failure in User Equipment (UE) registration with a first Stand-alone Private Network (SNPN) cell selected to avail localized services in a Tracking Area (TA); adding, by the UE, at least one Group ID for Network (GIN) and a current Tracking Area Identity (TAI) comprising at least one Tracking Area Code (TAC) of the TA associated with the at least one GIN broadcasted by the first SNPN cell, to a forbidden list among a plurality of forbidden lists associated with the first SNPN cell, upon receiving the MM reject cause message; receiving, by the UE, Steering of Roaming SNPN Selection Information for Localized Services (SOR-SNPN-SI-LS) information from a second SNPN cell selected to avail the localized services in the TA, upon successful UE registration with the second SNPN cell, wherein the SOR-SNPN-SI-LS information comprises entries indicating at least one GIN and at least one TAC of the TA included in location validity information corresponding to the at least one GIN; determining, by the UE, occurrence of a match when, the at least one TAC included in the current TAI added to the forbidden list is associated with the at least one GIN indicated as an entry in the SOR-SNPN-SI-LS information, and the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list; and deleting, by the UE, the TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list, to avail the localized services in the TA from the second SNPN cell using the TA associated with the at least one TAC deleted from the forbidden list, upon determining occurrence of the match.

[0278] According to an embodiment of the present disclosure, the SOR-SNPN-SI-LS information comprises the entries indicating the at least one GIN and the at least one TAC of the TA included in the location validity information corresponding to the at least one GIN in “credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN”.

[0279] According to an embodiment of the present disclosure, the adding the at least one GIN and the current TAI comprising the at least one TAC associated with the at least one GIN to the forbidden list comprises: storing the at least one GIN and the current TAI comprising the at least one TAC associated with the at least one GIN broadcasted by the first SNPN cell in one of the plurality of forbidden lists comprising "5GS forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for roaming", and “forbidden tracking area list corresponding to other Radio Access Technologies (RATs)”, for the first SNPN cell, and a selected entry of "list of subscriber data" or a selected PLMN subscription.

[0280] According to an embodiment of the present disclosure, wherein prior to receiving the MM reject cause message, the method comprises, receiving, by the UE, broadcasted information comprising an identifier of the first SNPN cell, the at least one GIN, and the at least one TAC associated with the at least one GIN.

[0281] According to an embodiment of the present disclosure, wherein upon receiving the MM reject cause message, the method comprises, triggering, by the UE, the UE registration with the second SNPN cell to avail the localized services.

[0282] According to an embodiment of the present disclosure, wherein deleting the TA associated with the at least one TAC comprises, deleting, by the UE, TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the forbidden list associated with the first SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, when the at least one TAC of the tracking area(s) in the forbidden list is associated with the at least one GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN".

[0283] According to an embodiment of the present disclosure, A User Equipment (UE) for managing forbidden lists of Tracking Areas (TAs) in communication networks, comprising a processor, and a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which, on execution, causes the processor to: receive during a registration procedure, a Mobility Management (MM) reject cause message indicative of a failure in User Equipment (UE) registration with a first Stand-alone Private Network (SNPN) cell selected to avail localized services in a Tracking Area (TA), add at least one Group ID for Network (GIN) and a current Tracking Area Identity (TAI) comprising at least one Tracking Area Code (TAC) of the TA associated with the at least one GIN broadcasted by the first SNPN cell, to a forbidden list among a plurality of forbidden lists associated with the first SNPN cell, upon receiving the MM reject cause message, receive Steering of Roaming SNPN Selection Information for Localized Services (SOR-SNPN-SI-LS) information from a second SNPN cell selected to avail the localized services in the TA, upon successful UE registration with the second SNPN cell, wherein the SOR-SNPN-SI-LS information comprises entries indicating at least one GIN and at least one TAC of the TA included in location validity information corresponding to the at least one GIN, determine occurrence of a match when, the at least one TAC included in the current TAI added to the forbidden list is associated with the at least one GIN indicated as an entry in the SOR-SNPN-SI-LS information, and the at least one GIN indicated as the entry in the SOR-SNPN-SI-LS information matches with the at least one GIN added to the forbidden list, and delete the TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN received as the entry of the SOR-SNPN-SI-LS information, from the forbidden list, to avail the localized services in the TA from the second SNPN cell using the TA associated with the at least one TAC deleted from the forbidden list, upon determining occurrence of the match.

[0284] According to an embodiment of the present disclosure, the SOR-SNPN-SI-LS information comprises the entries indicating the at least one GIN and the at least one TAC of the TA included in the location validity information corresponding to the at least one GIN in “credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN”.

[0285] According to an embodiment of the present disclosure, to add the at least one GIN and the current TAI comprising the at least one TAC associated with the at least one GIN to the forbidden list, the processor is configured to: store the at least one GIN and the current TAI comprising the at least one TAC associated with the at least one GIN broadcasted by the first SNPN cell in one of the plurality of forbidden lists comprising "5GS forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for roaming", and “forbidden tracking area list corresponding to other Radio Access Technologies (RATs)”, for the first SNPN cell, and a selected entry of "list of subscriber data" or a selected PLMN subscription.

[0286] According to an embodiment of the present disclosure, wherein prior to receiving the MM reject cause message, the processor is configured to: receive broadcasted information comprising an identifier of the first SNPN cell, the at least one GIN, and the at least one TAC associated with the at least one GIN.

[0287] According to an embodiment of the present disclosure, wherein upon receiving the MM reject cause message, the processor is configured to: trigger the UE registration with the second SNPN cell to avail the localized services.

[0288] According to an embodiment of the present disclosure, wherein to delete the TA, the processor is configured to: delete TA associated with the at least one TAC included in the location validity information corresponding to the at least one GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the forbidden list associated with the first SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, when the at least one TAC of the tracking area(s) in the forbidden list is associated with the at least one GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN".

[0289] Equivalents:

[0290] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention. When a single device or article is described herein, it will be apparent that more than one device / article (whether or not they cooperate) may be used in place of a single device / article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be apparent that a single device / article may be used in place of the more than one device or article, or a different number of devices / articles　may be used instead of the shown number of devices or programs. The functionality and / or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality / features. Thus, other embodiments of the invention need not include the device itself.

[0291] The specification has described a system and a method for performing edge federation in the federated network. The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that on-going technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words "comprising," "having," "containing," and "including," and other similar forms are intended to be equivalent in meaning and be open-ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.

[0292] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

[0293] Referral numerals

[0294]

[0295]

Claims

1.A method performed by a user equipment, UE, in a wireless communication system, the method comprising:receiving, from an access and mobility management function (AMF) entity of a first stand-alone non-public network (SNPN) selected for a localized service, a registration reject message of a first registration procedure, the registration reject message including a mobility management (MM) reject cause; andstoring, based on the MM reject cause, a current tracking area identity (TAI) of a tracking area (TA) in a forbidden TA list for the first SNPN and a selected entry of list of subscriber data or a selected PLMN subscription along with a group identification for network (GIN).2.The method of claim 1,wherein the GIN is broadcasted by the first SNPN.3.The method of claim 1,wherein the forbidden TA list includes a 5GS forbidden tracking areas for regional provision of service, or a 5GS forbidden tracking areas for roaming.4.The method of claim 3,wherein the MM reject cause includes:a first reject cause indicating that the TA is not allowed,a second reject cause indicating that roaming is not allowed in the TA, ora third reject cause indicating that there are no suitable cells in the TA.5.The method of claim 1, further comprising:receiving, from the AMF entity, steering of roaming SNPN selection information for localized services (SOR-SNPN-SI-LS), wherein the SOR-SNPN-SI-LS comprises at least one GIN and location validity information including the TA; andin case that the TA in the forbidden TA list is associated with the GIN of the at least one GIN, deleting the TA corresponding to the GIN from the forbidden TA list.6.The method of claim 5, wherein the SOR-SNPN-SI-LS includes a credentials holder controlled prioritized list of preferred GINs for access to the localized service with an entry comprising the at least one GIN and the location validity information.7.The method of claim 5,wherein the SOR-SNPN-SI-LS is received based on a second registration procedure for access to the SNPN with a TA different from the TA included in the forbidden TA list selected for the localized service.8.The method of claim 7,wherein the SOR-SNPN-SI-LS is received after the second registration procedure.9.A user equipment, UE, comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive, from an access and mobility management function (AMF) entity of a first stand-alone non-public network (SNPN) selected for a localized service, a registration reject message of a first registration procedure, the registration reject message including a mobility management (MM) reject cause, andstore, based on the MM reject cause, a current tracking area identity (TAI) of a tracking area (TA) in a forbidden TA list for the first SNPN and a selected entry of list of subscriber data or a selected PLMN subscription along with a group identification for network (GIN).10.The UE of claim 9,wherein the GIN is broadcasted by the first SNPN.11.The UE of claim 9,wherein the forbidden TA list includes a 5GS forbidden tracking areas for regional provision of service, or a 5GS forbidden tracking areas for roaming.12.The UE of claim 11,wherein the MM reject cause includes:a first reject cause indicating that the TA is not allowed,a second reject cause indicating that roaming is not allowed in the TA, ora third reject cause indicating that there are no suitable cells in the TA.13.The UE of claim 9, wherein the instructions further cause the UE to:receive, from the AMF entity, steering of roaming SNPN selection information for localized services (SOR-SNPN-SI-LS), wherein the SOR-SNPN-SI-LS comprises at least one GIN and location validity information including the TA; andin case that the TA in the forbidden TA list is associated with the GIN of the at least one GIN, delete the TA corresponding to the GIN from the forbidden TA list.14.The UE of claim 13, wherein the SOR-SNPN-SI-LS includes a credentials holder controlled prioritized list of preferred GINs for access to the localized service with an entry comprising the at least one GIN and the location validity information.15.The UE of claim 14,wherein the SOR-SNPN-SI-LS is received based on a second registration procedure for access to the SNPN with a TA different from the TA included in the forbidden TA list selected for the localized service,wherein the SOR-SNPN-SI-LS is received after the second registration procedure.

Images